Home / Taxonomy term

caching

Drupal 8 performance: render caching

In late 2009, Drupal 7 introduced render caching — enabling Drupal modules to easily cache the final HTML corresponding to a subtree in a Drupal render array. Render caching already was a powerful tool in Drupal 7, but unfortunately almost nobody knew about it! This blog post will show how you can leverage it, how it's gotten even better in Drupal 8, and how you will be leveraging it directly in Drupal 8. Hopefully I can get you excited :)

When and how caching can save your site. Part 2: authenticated users

On my last blog post we looked to what Drupal achieves out of the box regarding Drupal caching. We understood how Drupal can cache pages for anonymous users and found solutions to avoid to bootstrap Drupal to serve a cached page (using a reverse proxy like Varnish or redirecting requests using Boost). We also saw that even if any of these tools is used, Drupal is also able to save cached versions of pages in the database. However, Drupal allows to plug transparently other caching backends that are faster: