This module enables to create the cached wrapper of any block. It can be used where standard block caching is disabled if node access modules are installed.
This module is aimed at providing a powerful yet lightweight caching option for sites that use views and panels. It can be considered as a faster and more advanced alternative to the standard caching provided by views/panels (also when they are combined with rules and cache_actions contribs).
Extends Acquia Purge to allow for placing a block on a page for "purge this page" functionality. Addresses the situation of when you want to grant permissions to a content edit who doesn't have administrative privileges so that they can purge the Varnish cache of any given page if they notice any content (node, block, views) is stale.
DEPENDENCIES
Dependent on versions of Acquia Purge with the acquia_purge_purge_path() function, introduced in 1.0-beta2.
In the Acquia Cloud platform, you can redirect site visitors in the Varnish layer, based on the devices they are using, as determined by the user-agent HTTP header in the request. You can do this by using your web site's .htaccess file to set HTTP headers in the response.
However, when you configure Acquia Cloud to use PHP-FPM, the .htaccess file is no longer parsed and these redirects stop working. To get the redirect headers to output, you'll need to run some PHP code.
For complex sites with a lot of content, entity lookups can be extremely expensive. This module attempts to flatten the key information in an easily searchable table.
Idea : This module will address the performance needs of the Drupal site by analyzing various performance aspects of the site and provide the detailed performance report.
