Full text magento cache with memcached

Question

I am trying to get the full Magento cache using memcached.

I understand that there is some configuration that needs to be installed in the app / etc / enterprise.xml file, but there seems to be no documentation giving specific information about what this configuration should do.

From what I read, it looks like memcached configuration in app / etc / local.xml, but not quite the same.

Does anyone have this job, who can provide the appropriate configuration options?

Answer 1

The full page key can be enabled on the admin cache management page. To save the full page cache in memcache, you will need the following configuration. This XML file can be found in app/etc/local.xml.additional and must be added to regular local.xml .

Keep in mind that you want your cache and FPC sessions to be stored in a different memcached cache. Otherwise, clearing memcache will also log out all your clients. Flushing memcache can be done by the administrator using Flush Cache Storage .

Obviously, this is only the side of Magento, you also need to configure and run memcache on your server.

 <config> <global> <session_save><![CDATA[]]></session_save> <!-- db / memcache / empty=files --> <session_save_path><![CDATA[]]></session_save_path><!-- eg for memcache session save handler tcp://10.0.0.1:11211?persistent=1&weight=2&timeout=10&retry_interval=10 --> <session_cache_limiter><![CDATA[]]></session_cache_limiter><!-- see http://php.net/manual/en/function.session-cache-limiter.php#82174 for possible values --> <cache> <backend></backend><!-- apc / memcached / xcache / empty=file --> <slow_backend></slow_backend> <!-- database / file (default) - used for 2 levels cache setup, necessary for all shared memory storages --> <slow_backend_store_data></slow_backend_store_data> <!-- 1 / 0 (default) - used for 2 levels cache setup, sets whether store data in db slow cache backend --> <auto_refresh_fast_cache></auto_refresh_fast_cache> <!-- 1 / 0 (default) - used for 2 levels cache setup, sets whether refresh data in fast cache backend --> <memcached><!-- memcached cache backend related config --> <servers><!-- any number of server nodes can be included --> <server> <host><![CDATA[]]></host> <port><![CDATA[]]></port> <persistent><![CDATA[]]></persistent> <weight><![CDATA[]]></weight> <timeout><![CDATA[]]></timeout> <retry_interval><![CDATA[]]></retry_interval> <status><![CDATA[]]></status> </server> </servers> <compression><![CDATA[0]]></compression> <cache_dir><![CDATA[]]></cache_dir> <hashed_directory_level><![CDATA[]]></hashed_directory_level> <hashed_directory_umask><![CDATA[]]></hashed_directory_umask> <file_name_prefix><![CDATA[]]></file_name_prefix> </memcached> </cache> <!-- example of two level cache setup with slow backend at files. --> <full_page_cache> <backend_options> <cache_dir>full_page_cache</cache_dir> </backend_options> <slow_backend_options> <hashed_directory_level>1</hashed_directory_level> <hashed_directory_umask>0777</hashed_directory_umask> <file_name_prefix>fpc</file_name_prefix> <cache_dir><![CDATA[full_page_cache]]></cache_dir> </slow_backend_options> </full_page_cache> <remote_addr_headers><!-- list headers that contain real client IP if webserver is behind a reverse proxy --> <header1>HTTP_X_REAL_IP</header1> <header2>HTTP_X_FORWARDED_FOR</header2> </remote_addr_headers> </global>