Performance

Borrowed pane allows grouped caching and client-side re-use of rendered elements on a page.

Use cases

Grouped caching

When using mini-panels it is ideal to cache the entire mini-panel rather than cache the individual panes within the mini-panel.

The problem is that the mini-panel often contains one or more panes that are unique to the current page via context, the current page path, current user, etc.

Instead of rendering the unique content within the mini-panel you render the content elsewhere on the page, in an area that is not within a mini-panel you'd like completely cached. You then place a borrowed pane in each of the locations you need the unique content displayed within your mini-panel and specify the jQuery selectors to the content you'd like loaded into the pane.

Responsive support

When a site is built to be responsive, there are often times where it would be convenient to have a rendered pane/block appear in multiple places within the DOM.

The problem is that adding the same DOM to a page in multiple places is not ideal for SEO. Nor is it good from a performance standpoint to re-render the same DOM in multiple instances on a single page.

Navbar Flush Cache is a module which adds functionality to the Navbar module allowing users to flush the cache from the menu.

Module qui supprime les groupes dans les fichiers css/js pendant l'optimisation des fichiers et permets de les fusionner encore d'avantage. Cela diminue le nombre de fichiers à télécharger

Public files URL is an extremely light weight module that allows you to override domain your public files system uses by extending the public file system wrapper in Drupal Core.

This module allows for hook_expire_cache() to be executed through a cron queue worker.

Drupal's building and rendering process of entities is quite time consuming. This module attempts to alleviate needless rebuilding and re-rendering of entities on subsequent page loads by caching.

When an entity is updated a new cache key is generated; there's no waiting for a cache to time out.

Currently this module only aims at caching rendered entities, however if you have an idea for other general render caching please submit an issue.

How to use

Unfortunately, there's no way to hook into core Drupal functions such as node_view() to provide caching of rendered entities site wide - I tried, a lot.

However the module entity API provides an entity_view() method which renders any entity type your site provides. This module hooks into that process and essentially hijacks any entity rendering to check for caching before rendering.

If your code base consistently uses entity_view() instead of node_view(), taxonomy_term_view(), etc, then render cache can improve your page build time dramatically.

render_cache_views module can also hijack the views node view row plugin, bundled with the views module, to provide render caching.

render_cache_ds module can also hijack the views display suite row plugin, bundled with the ds module, to provide render caching.

Render cache can also take over the node/% router path and provide caching for those entities by enabling the render_cache_node module.

render_cache_comments module can hijacks the default comments display from node module.

render_cache_context can also cache blocks placed by context module.