[wp-trac] Re: [WordPress Trac] #5550: ENABLE_CACHE and DISABLE_CACHE constants

WordPress Trac wp-trac at lists.automattic.com
Wed Jan 2 18:18:56 GMT 2008

#5550: ENABLE_CACHE and DISABLE_CACHE constants
 Reporter:  Mrasnika      |        Owner:  anonymous
     Type:  defect        |       Status:  new      
 Priority:  normal        |    Milestone:  2.5      
Component:  Optimization  |      Version:  2.3.2    
 Severity:  major         |   Resolution:           
 Keywords:  cache         |  
Comment (by ryan):

 Replying to [comment:4 Mrasnika]:
 > Replying to [comment:2 ryan]:
 > > A better option might be to not do any serializing when the persistent
 cache is not being used.
 > That's exactly what I am trying to say - when the WP_Object_Cache is
 off, there should not be any serialization done.
 > And instead of DISABLE_CACHE=true, I must do ENABLE_CACHE=false, correct

 But this patch avoids serialization by completely avoiding the in-memory
 cache.  This will result in lots of DB queries.

 DISABLE_CACHE is a misnomer.  That disables the persistent cache only, not
 the entire cache.  We'll probably be removing the default persistent
 caching, leaving that to plugins.  The persistent cache is not enabled by
 default anyway.  With persistence removed, I think we can lose the
 unserialize(serialize()) calls.

Ticket URL: <http://trac.wordpress.org/ticket/5550#comment:6>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list