A site we have been administring for several months has memcache. We use memcache.inc, not the db backed one. We don't use memcache for sessions. The configuration is straight forward with only 3 bins (page, filter, and everything else).

When upgrading from 6.x-12 to 6.x-1.3, we saw more cache hits on the cache_page bin (which should be good), but also higher database utilization. Reverting back to 6.x-12 reduced the database and CPU load on the server, although with less cache hits.

The details with graphs are documented here.

What can that be?

Comments

jeremy’s picture

jeremy commented

I believe this is the same bug:
#539108: cache_set should not accept number of seconds as a valid expires-value

Expire would be set to -1, which would then be considered less than time(), which would mean that the page cache would be rebuilt immediately. :/

Sadly, cache hits are going to be a little misleading in 6.x-1.3+. It may prove useful to (at least optionally) track our own stats.

jeremy’s picture

jeremy commented
Status: Active » Fixed

Fix applied:
http://drupal.org/cvs?commit=246944

kbahey’s picture

kbahey commented

Jeremy,

I can confirm that 6.x-1.4-rc1 did fix the issue reported with 1.3, and also provided a positive boost more than 1.2.

So, job well done here. You should mark 1.3 as defective or have it unpublished, and tag a new 1.4 stable.

I have the graphs if you are interested. Perhaps I will post them on the article linked above if there is interest.

jeremy’s picture

jeremy commented

Yes, additional graphs would be very welcome. Glad to hear that it's fixed things for you.

kbahey’s picture

kbahey commented

Jeremy, the article on 2bits.com has been updated with new graphs. Very positive change.

jeremy’s picture

jeremy commented

Awesome, thanks! Looks good. :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.