You are here

Home » API reference » Acquia Purge 6

README.txt in Acquia Purge 6 

Readme
================================================================================
The Acquia Purge module allows Drupal sites hosted on Acquia Cloud to
automatically purge (wipe) pages from their Varnish powered load balancers, as
soon as content actually changed. The higher Drupal's "expiration of cached
pages"-setting (TTL) is configured the more your site will be served directly
off your load balancers. This effectively increases the efficiency of your site
and lowers hardware costs, leaving more resources for back-end traffic. In most
scenarios the module offers a full turn-key experience without requiring any
technical configuration.

Features:
 * Built with editorial people and end-users in mind.
 * On-screen progressbar showing pages being cleared and made public.
 * Turn-key installation for simple content sites.
 * Wipes pages based on detected changes by the expire module.
 * Integration with Rules allowing to wipe pages like 'news' and 'contact'.
 * Transparently wipes pages from Drupal's page cache.
 * Detects your Acquia Cloud domain names allowing manual overriding.
 * Support for both Domain Access and multi-site setups.
 * Detailed watchdog logging on everything that happens.
 * Atomic operation based on AJAX and the Queue API.
 * Manual purge feature for emergency administration needs.
 * Drush: ap-diagnosis, ap-domains, ap-forget, ap-list, ap-process, ap-purge.

Why do I need this?
================================================================================
Throughout the years the Acquia Support department has seen thousands of Drupal
sites pass by on daily basis and one of the most typical things we have noticed
is that many sites run with a very low "expiration of cached pages"-setting
(e.g. 5 minutes). This means that every single page ever generated by Drupal
will be cached very shortly by your load balancer and regenerated for no reason
just a couple of minutes after that. This puts your web servers under the
constant task of generating pages regardless if they actually changed or not.

By applying proactive purging on your site, it will actively tell your load
balancers what pages to forget while keeping the others in cache for much
longer. This hugely decreases the stress on your web servers and leaves more
"PHP processes" available for actual back-end traffic. Basically every site will
benefit from implementing this, especially content-focused sites like news
sites, blogs and brand sites.

File

README.txt
View source 
  1. Readme

  2. ================================================================================

  3. The Acquia Purge module allows Drupal sites hosted on Acquia Cloud to

  4. automatically purge (wipe) pages from their Varnish powered load balancers, as

  5. soon as content actually changed. The higher Drupal's "expiration of cached

  6. pages"-setting (TTL) is configured the more your site will be served directly

  7. off your load balancers. This effectively increases the efficiency of your site

  8. and lowers hardware costs, leaving more resources for back-end traffic. In most

  9. scenarios the module offers a full turn-key experience without requiring any

  10. technical configuration.

  11. 

  12. Features:

  13.  * Built with editorial people and end-users in mind.

  14.  * On-screen progressbar showing pages being cleared and made public.

  15.  * Turn-key installation for simple content sites.

  16.  * Wipes pages based on detected changes by the expire module.

  17.  * Integration with Rules allowing to wipe pages like 'news' and 'contact'.

  18.  * Transparently wipes pages from Drupal's page cache.

  19.  * Detects your Acquia Cloud domain names allowing manual overriding.

  20.  * Support for both Domain Access and multi-site setups.

  21.  * Detailed watchdog logging on everything that happens.

  22.  * Atomic operation based on AJAX and the Queue API.

  23.  * Manual purge feature for emergency administration needs.

  24.  * Drush: ap-diagnosis, ap-domains, ap-forget, ap-list, ap-process, ap-purge.

  25. 

  26. Why do I need this?

  27. ================================================================================

  28. Throughout the years the Acquia Support department has seen thousands of Drupal

  29. sites pass by on daily basis and one of the most typical things we have noticed

  30. is that many sites run with a very low "expiration of cached pages"-setting

  31. (e.g. 5 minutes). This means that every single page ever generated by Drupal

  32. will be cached very shortly by your load balancer and regenerated for no reason

  33. just a couple of minutes after that. This puts your web servers under the

  34. constant task of generating pages regardless if they actually changed or not.

  35. 

  36. By applying proactive purging on your site, it will actively tell your load

  37. balancers what pages to forget while keeping the others in cache for much

  38. longer. This hugely decreases the stress on your web servers and leaves more

  39. "PHP processes" available for actual back-end traffic. Basically every site will

  40. benefit from implementing this, especially content-focused sites like news

  41. sites, blogs and brand sites.