Views - Cache - Single View

You can configure caching on a single view, by looking at the advance settings for that view.  First navigate to the views page at: admin/structure/views/view/ and select your view by clicking the edit button in the far right column.

Click the edit button on the far right.

With your view in edit mode, expand the Advanced criteria in the right hand column to see the advance settings for this view and this view only.

The red arrow indicates the location of the advanced settings.

Under the Other subgrouping there is a link to caching. By default caching is set to None.

Click the None.

Drupal per view caching is time based.  It can be applied to all the displays of a view or a single display of a view.

We are configuring the cache for this display (page) and not the block.  The block instance of the view will not be cached.

If you want caching select the display and click the Time-based radio button and click Apply.

From here you can set the query results and rendered output caches.

There are two confusing options for views caching.

These two options are difficult to understand and more difficult to explain.

  • Query Results - This is the caching of the database sql.  Hitting the database base and getting the results is time and cpu consuming.  If you can reduce the hits to the database, your site will be quicker.
  • Rendered output - This is after the results have been retrieved from the database and digested by Drupal.

Check to the upper right under quick hints for a better and clearer explanation!

If you want to learn how to set caching for all your views, click here.

Cron will control your caching.  Take a look at our cron page.