[wp-hackers] Bizarre /cache/ experience with wp_object_cache.lock

[David Chait]

+1  Given the 'marginal gains', and given that it does absolutely freaky 
things if it is in a bad state (one case was caught, you've hit another), 
object caching should be DISABLED by default, and require enabling by an 
advanced user (given 'average' shared hosting user won't see much of a 
gain -- say compared to the wp-cache factors...).

----- Original Message ----- 
From: "Mark Jaquith" <mark.wordpress at txfx.net>
To: <wp-hackers at lists.automattic.com>
Sent: Friday, February 03, 2006 7:00 AM
Subject: Re: [wp-hackers] Bizarre /cache/ experience with 
wp_object_cache.lock


| On Feb 3, 2006, at 6:02 AM, David House wrote:
|
| > At the moment we have a constant,
| > ENABLE_CACHE, which you can define in wp-config.php to enable the
| > cache even when safe mode is on.
|
| We'll still need an option if we want to automatically disable the
| cache when it isn't working an avoid those 300+ query loads.  The
| average user (a) isn't going to know that 300 queries are being made)
| and (b) probably won't figure out very quickly how to do define
| ('DISABLE_CACHE', true); to revert to the old cache method.
|
| --
| Mark Jaquith
| http://txfx.net/
|
|
| _______________________________________________
| wp-hackers mailing list
| wp-hackers at lists.automattic.com
| http://lists.automattic.com/mailman/listinfo/wp-hackers
|