I am facing some troubles while using memcache engine in shared mode.

The lookup key of cache becomes bigger than 1MB. This means that set() fails and resets the content of the lookup key.
When such problem occurs, the previous content of the cache table is not referenced any more in the lookup entry. These unreferenced cache entries will never be flushed during the next calls to delete().

Even if I am not sure it will solve my problem, I am wondering why the compress parameter is not used when calling set() on the lookup?

CommentFileSizeAuthor
#1 cacherouter-memcache.php-compress_lookup-1144392-1.patch1.07 KBatouchard
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

atouchard’s picture

atouchard CreditAttribution: atouchard commented
FileSize
cacherouter-memcache.php-compress_lookup-1144392-1.patch1.07 KB

Is there any reason not to compress in shared mode like this (see the patch) ?

Thanks

andypost’s picture

andypost
he/him
Primary language Russian
CreditAttribution: andypost commented
Version: 6.x-1.0-rc1 » 6.x-1.x-dev
Status: Active » Needs review

The reason been to avoid CPU regression because lookups could be frequently used within each request.

So we have to choose between performance and memory usage. Memcache's 1mb limit is huge bottleneck