I have a Magento installation running on LEMP Stack; Nginx + PHP-FPM (PHP v5.5.6 w/ APCu v4.0.2) + Percona.

I've configured my magento to use APCu caching like this:



and the APC is configured like this:



apc.enabled          = 1
apc.shm_segments     = 1
apc.shm_size         = 512M
apc.ttl              = 7200
apc.user_ttl         = 7200
apc.num_files_hint   = 10240
apc.mmap_file_mask   = /tmp/apc.XXXXXXX
apc.enable_cli       = 1
apc.cache_by_default = 1
apc.max_file_size    = 10M
apc.stat             = 1

and here's the apc info page displaying the huge miss to hit ratio:

enter image description here

Any idea what might be wrong?


You can read more information on why it is happening here: http://magebase.com/magento-tutorials/improving-the-file-cache-backend/


Don't use APC as a cache Backend for Magento.

In a nutshell, the APC Zend Cache Backend can only be used for the actual cache records.
Magento automatically uses the Zend Two Level Cache Backend in conjunction with the regular File Cache Backend to save the cache meta data (cache tags) when the APC cache backend is configured.

Instead, use https://github.com/colinmollenhour/Cm_Cache_Backend_File for single webserver instances.
It is much faster and scales better by an order of magnitude then the APC-File cache backend combo.
If you are using more then one webserver, use https://github.com/colinmollenhour/Cm_Cache_Backend_Redis, which has also been included in the core (CE+EE) since a couple of versions now.

To benchmark your cache setup I can recommend https://github.com/colinmollenhour/magento-cache-benchmark

  • have a small question.is it good idea to use APUc instead of APU? – Amit Bera Dec 9 '16 at 7:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.