Fast cache

Component type

module

Maintenance status

Development status

Downloads

1118

Component created

Component changed

Looking for a co-maintainer - contact beejeebus if you're interested!

Fasterer caching on multi-webheaded Drupal installs. This module will try to get cache items from a fast cache (probably local, like APC), then fallback to a central, consistent cache. Local cache items are only used if they are newer than the last write to the central cache bin they are in front of.

Ideally your fast cache will be APCu, and your central cache will be Memcache or Redis

Heisencache

Component type

module

Maintenance status

Development status

Downloads

65

Component created

Component changed

Positioning

Heisencache is a cache monitoring tool for developers: it has an API but no significant UI (roll your own).

It provides the ability to catch all cache requests, triggering events before and after each of them, and providing predefined subscribers to handle them, as well as the freedom to add whatever subscribers the developer wishes to perform data slicing, dicing, and reporting.

Development

Contributions are welcome. The project has received some from France Televisions and Amazee Labs. Most useful would be UI development.

Redis routing

Component type

module

Maintenance status

Development status

Component created

Component changed

Redis for Routing

==========

This project replace the routing db storage to redis storage.

This module use a Predis library to connect on Redis service, in Drupal 8 the composer.json is versioned in core what is a problem because this module need load the predis library before to load Drupal bootstrap.

Advanced Page Expiration

Component type

module

Maintenance status

Development status

Downloads

12848

Component created

Component changed

Advanced control of your cache-control header

Advanced Page Expiration addresses the use cases of needing certain pages on the site to expire faster than other pages. For example, using this module all pages on the site could be cached for 24 hours except for the homepage which could be cached for five minutes.

Hello Baseline

Component type

module

Maintenance status

Development status

Component created

Component changed

The intention of this module is to have a few quick ways to test Drupal baseline performance on a site.

For example, by visiting "hello-baseline/basic" the page will simply return a string of "Hello World" allowing benchmarking tool such as XHProf to get a sense of what the load for the simplest content page would be.

A more robust solution for testing baseline performance can be found here, although I have never tried it myself: https://drupal.org/project/baseperf

Views Accelerator

Component type

module

Maintenance status

Development status

Downloads

5644

Component created

Component changed

For those not reading the full project page or the README: this module improves speed by rendering Views fields simpler and more efficiently. If you find that after turning the accelerator on for a view, fields don't render quite as expected and the tips in the README don't help, then you should switch the accelerator off for that view.

Views Accelerator can bring about significant speed improvements on sites with views that cannot be cached normally, for instance because the views depend on an aspect of the visitor's session, like their location.
Views Accelerator serves up two modes of operation.

  • Analysis mode:
    Switched on from the module's configuration page, admin/config/system/views-accelerator, this displays at the top of the screen a performance summary for each view on the page. If performance is already great, tell your boss or customer. If it isn't, take a screenshot of the performance summary and proceed with the
  • Accelerator mode:
    On views that could do with a boost, find and click the Caching option link in the Advanced section of the Views UI. It will reveal a new pseudo-caching option: None. Post-execution optimized by Views Accelerator. Select that. Revisit the page with the view(s) and compare performance stats to the screenshot you took earlier. Win? Then tell your boss or customer.