Magento 2 set private cache how to#

Instead they are a reflection of the values that will already have been set up when configuring Varnish and are actually used to generate the Varnish Configuration Language (VCL) file when one of the “Export VCL for Varnish” buttons at the bottom is clicked. These settings are actually a bit misleading, as they don’t actually affect the Varnish integration.

That’s because Varnish is now listening on port 80 and receiving all inbound HTTP traffic, and forwarding requests to port 8080 when needed.Īs you can see from the screenshot, selecting the Varnish option reveals a subsection of configuration options relating to the Varnish server. apache, nginx) to use port 8080 instead of the default port 80. This change needs to be done in parallel with a modification to the web server (e.g. When the Varnish option is selected Magento 2 delegates FPC caching to the Varnish server.

Magento 2 set private cache how to#

It in turn points to the official documentation on how to install Varnish. Magento has really improved its support material and this is a great resource. The Varnish FPC optionīefore proceeding to discuss Varnish I’ll point you to the documentation on installing and configuring Varnish with Magento 2. apache, nginx) and so Magento must still handle all requests, even for a fully cached page, and needs to be bootstrapped to achieve this. However, the reason why it will never be able to deliver the performance levels of the Varnish option is because all traffic is still routed through the web server (e.g. So the built-in option is more robust than it initially appears and is probably quite adequate for supporting low traffic production sites, assuming it is configured to use something like Redis. However, the FPC functions completely independently in Magento 2 so it will actually fall back to the file system if the page_cache array key is removed. Users familiar with Magento 1 might expect that removing the page_cache array key would cause the FPC to fall back to using the default cache settings and continue to use Redis. The page_cache array key configures the built-in FPC to use the same redis instance but database 1 instead. config, layout, block) to be stored in a Redis instance using database 0. The default array key configures the regular cache sections (e.g. Here we see a default and page_cache array key defined under a frontend array key (where the term frontend refers to a cache frontend, rather than the frontend configuration namespace).

However, like its Magento 1 predecessor it has the benefit of being configurable so that the caching storage can use a few different external applications, including Redis and database (the default is file system).Īlso, like Magento 1, the FPC cache storage configuration is separated from the rest of the cache storage configuration. This might cause it to be dismissed as lightweight. As you can see from the screenshot, the built-in option comes with a rather obvious disclaimer that it is not recommended for production use.