"Total hits" in Memcache statistics table are always at 0%. Does my memcache work?

Makes me wonder if you actually installed a Memcached server service, added the memcached or memcache php extension, and configured them as described in the module README.

Thanks for reply @fgm.

It's a shared sever with cPanel.

These screenshots may help:

- cPanel PHP extensions screenshot
- Status page screenshot
- phpinfo() screenshot
- Memcache statistics (turned on by Memcache admin module) screenshot

BTW... one more question.

I couldn't find any information regarding core "Internal Page Cache" and "Internal Dynamic Page Cache" modules when using Memcache.

Should I uninstall this two core modules or should they stay installed? Or it doesn't matter?

IPC and DPC are just modules implementing specific cache bins. They will be in memcache if you configured the site in the basic memcache configuration.

I just did a fresh install to check and I just get 100% hits on get/set and 92% on getMulti.

One thing I've noticed from helping with the elijaa/phpmemcacheadmin project is that over time, Memcached (the daemon) changes the implementation of the debug information and admin tools like the Memcache Admin module (or in my case phpmemcacheadmin) have to support multiple versions of the debug schema. It could be that the version of memcached on your machine does not match the one supported by this module.

You could try checking your memcached instance with phpmemcached admin or any other tool just to be sure they also show 0% hits. If they also show 0, the problem is probably in your Drupal configuration. If they show nonzero, it's probably a mismatch between your Memcached daemon version, the extension, and the Drupal code.

Looks like you will have to do some debugging to do. And beware, because this is something which will vary from one infrastructure to another. You could very well have the problem on a given cPanel hosting and not have it when debugging locally on your machine, for example.
And/or wonder if maybe you could just not be using memcached, which is something useful only on the biggest sites (multi-million hits/day).

Smaller ones tend to fare well with the core DB cache, actually; or Redis for medium-large ones.

If you really need Memcached and cannot perform that debugging, some companies can provide this kind of debugging, like Tag1, 2Bits Inc., or my own OSInet.

Thank you so much @fgm for your elaborated reply.

I have a rather small site, so switching back to db cache makes a lot of sense.

I'll close this issue as "Cannot reproduce", and maybe someone else will open it again in the future if he/she experience the same issue.

Thanks again! Have a nice holydays!