The core caches in Drupal are the page and block caches. In addition, you can use Drupal modules to cache views, panels, and entities, or to cache pages for authenticated users. You can also implement caching in custom code, using the Drupal Cache APIs.
On Acquia Cloud, you may not want to use Drupal's stock caching mechanisms for everything. See Disabling the Drupal cache for an explanation of why Varnish can do a better job for your website.
The main Drupal cache is a page cache; it caches complete pages. This means that the page cache has limited value if your website (like many) personalizes each page for signed-in visitors. Even a simple personalized welcome message on a page means that the identical page is unlikely to exist in the cache and must be regenerated for each page request.
By default, Drupal doesn't enable page caching; without it, every time a user visits a page, Drupal rebuilds the page. Page caching isn't in effect for users logged in to Drupal, but you should enable page caching for any website that receives any anonymous traffic.
To enable page caching, see the instructions for Configuring Drupal cache settings for Varnish.
For greater detail on Drupal page caching mechanisms, see How Drupal page cache works.
By default, Drupal doesn't cache individual blocks. While anonymous users will see cached blocks if you have page caching enabled, you should enable block caching on all websites to speed up page browsing for logged-in users.
- Sign in to your website using an account with administrator privileges.
- Go to the Performance page at Configuration > Performance (site path).
- Select the Cache blocks check box.
- Click Save configuration.
If your website has some blocks that prevent you from enabling block caching, consider the AJAX Blocks module.
Additional caching information
For more information about caching on your Drupal website, see the Caching overview Help Center article.