Magento 2 – Does Setting Cacheable False on Block Invalidate Full Page Cache?

After some digging around and some useful feedback on twitter I appear to have found some stuff out.

By default this is set-up to use a Zend Server feature Page Cache. It appears to be a feature almost completely set-up on the server with the only things in Magento being.

A clean function that calls. page_cache_remove_all_cached_contents

public function clean()
{
    if (extension_loaded('Zend Page Cache') && function_exists('page_cache_remove_all_cached_contents')) {
        page_cache_remove_all_cached_contents();
    }
}

And the enabling and disabling the extension from the admin section, but all this does is show/hide the button on the cache page.

As you can see from the clean function if uses the extension Zend Page Cache, but the class does implement the interface Mage_PageCache_Model_Control_Interface so it does seem like it has been built with the possibility to be used with other external caching systems and not just Zend server.

Note: I have never used this or Zend server

from https://www.section.io/blog/magento-performance-magento-varnish-cache/

"One common mistake when using Magento 2 is believing that Magento 2’s built in “Full Page Cache” feature is sufficient for performance. The Full Page Cache mode is labelled by Magento as to be used in development mode, as developers are not able to see what is being cached and what is not being cached with this setting. In production, it is strongly recommended all Magento 2 stores use Varnish Cache for optimal performance."

• Magento recommends Varnish as the full page cache for a production site - the built in cache should be used for development.

• Install varnish and configure Magento with the hostname or ip address and port of your varnish server

• download a vcl configuration file generated by Magento to use with the varnish server.

• make sure you add the external cache to the Magento configuration

  php bin/magento setup:config:set --http-cache-hosts=varnishhost