Support » Plugin: W3 Total Cache » 0.10.0 – memcache problem

  • Resolved Octavian Iosif

    (@neo2121)


    With the change to memcache in the latest 0.10.0 update we found that object caching is not working properly.
    Most noticeable: admin-ajax.php takes around 10-20 seconds more to load (waiting for the Cache_Memcached->get function).
    We use memcache also for page and database caching, but those work just fine.
    Turning off only object caching fixed the issue on all websites we tested on.
    Is there anything we can do to turn off the latest changes, or something we can do server-side to make it work as intended?

    We’re using the memcached 3.1.3 (libmemcached 1.0.18) php extension, on php 7.2.22 fpm, apache, with a memcache server running on the same machine.

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @neo2121,

    I am sorry about the issue you are having with Memcached.
    Issue related to Memcached is already reported in our GitHub Public repo https://github.com/W3EDGE/w3-total-cache/issues/35#.
    Please try the fix provided there and give us feedback if it works for you.

    jushengwu123

    (@jushengwu123)

    @vmarko since the last update I found that object cache is not working , neither memcache nor redis , while page cache and database cache are all right .
    my site : http://jushengwu.com
    <!–
    Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/products/

    Object Caching 0/0 objects using memcache
    Database Caching 24/49 queries in 0.016 seconds using memcache

    Served from: jushengwu.com @ 2019-09-12 08:36:48 by W3 Total Cache
    –>

    jaypabs

    (@jaypabs)

    I have the same problem.

    BoUk

    (@bouk)

    Hi guys,

    I can confirm, that I have experienced same issue with 0.10.0 when using object caching and Memcached back-end. Suggested fix helped to resolve the issue in terms of slowness and site became speedy again, however seeing same as @jushengwu123 where debug info in footer is displaying.

    Object Caching 0/0 objects using memcache

    Can confirm same behavior when upgrading to 0.10.1. Site is fast again, but debug info doesn’t look quite right.

    Perhaps it’s just a minor problem in reporting, although at the same time it may mean, object cache is bypassed and is not working at all.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @jushengwu123 and @jaypabs,

    Have you updated W3 Total Cache to the latest 0.10.1 version?
    Also, try purging and restarting your Memcached.

    BoUk

    (@bouk)

    Hi Marko,

    Thanks for your response. As mentioned in my initial comment, I did try to upgrade to the latest 0.10.1. Haven’t tried to restart memcached instance though. Will do now and will let you know.

    Thanks a lot.

    BoUk

    (@bouk)

    Ok, I can now confirm that problem with reporting persists. Using 0.10.1, restarted Memcached and still seeing:

    Object Caching 0/0 objects using memcached

    Site is fast, but looks like object caching is not kicking in at all.

    Worth to mention, that I’ve got other sites hosted on the same box, using W3TC 0.9.7.5, where I am getting expected report:

    Object Caching 671/678 objects using memcached

    Any more thoughts?

    francescoscialacqua

    (@francescoscialacqua)

    Same problem. I have update to 0.10.1

    The following memcached servers are not responding or not running:

    Object Cache: 127.0.0.1:11211.
    Minify: 127.0.0.1:11211.
    This message will automatically disappear once the issue is resolved.

    All test out of the plugin going done.


    The problem appears from upgrade php version up to 7.0

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @francescoscialacqua,

    I am sorry about the issue you are having. Did the issue start after the 0.10.1 update?
    Have you tried restarting your Memcached server?
    Please check out our FAQ as you might need to check your Memcached config:
    https://github.com/W3EDGE/w3-total-cache/wiki/FAQ:-Installation:-PHP-Modules#install-memcached-module
    https://github.com/W3EDGE/w3-total-cache/wiki/FAQ:-Installation:-Memcached-Server

    francescoscialacqua

    (@francescoscialacqua)

    No. I think that the problem start from the update php version. Rolling back to 7.0 the 0.10.1 version is ok with memcached.

    I think it’a a compatibility problem.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @francescoscialacqua,

    Just to clarify:

    The problem appears from upgrade php version up to 7.0

    Rolling back to 7.0 the 0.10.1 version is ok with memcached

    Which PHP version caused the issue?

    francescoscialacqua

    (@francescoscialacqua)

    I have upgrade from 7.0 to 7.3 and it’s appears the problem. Going back I resolve.

    Thread Starter Octavian Iosif

    (@neo2121)

    The latest version fixed it, as did the fix on Github, thank you for the quick fix!

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @neo2121,
    Glad to know your issue is resolved!

    @francescoscialacqua, @bouk, Can you please enable debug for Object cache in Performance>General settings, Debug sub-box and save all settings? Inspect the element and share the results of W3TC HTML comment.

    BoUk

    (@bouk)

    Hi Marko,

    I can confirm, that when debug is enabled, I am getting following:


    Object Caching 16/328 objects using memcached

    Object Cache debug info:
    Caching: enabled
    Total calls: 328
    Cache hits: 16
    Total time: 0.0748
    Page Caching using disk: enhanced (User is logged in)

    When I disable debug mode, I am getting:

    Object Caching 0/0 objects using memcached
    Page Caching using disk: enhanced (User is logged in)

    Which would suggest, object cache is not kicking in, however I am noticing no performance drop, which makes me think it’s just a small bug in reporting, which in return makes us wrongly think object cache is not working correctly.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘0.10.0 – memcache problem’ is closed to new replies.