Performance

Are your views returning a 200 when it should return a 404? Views 404 is the answer! This is very helpful for any caching layer and it will help SEO.

Cache actions provides rules actions for clearing drupal caches.

It currently provides actions for:

• Clearing Drupal cache bins
• Clearing CSS/JS cache
• Clearing The cache of specific views
• Clearing The cache of specific panel pages
• Clearing The cache of specific mini panels

Dependencies

Cache actions only depends on the rules module. If you don't have views or panels, you only get the option of clearing the drupal cache bins and the CSS/JS cache. When views or panels are present, you get actions for clearing the cache of specific views and panels as well.

Compatibility

This module is compatible with:

• Panels 3
• Views 2 and 3. The views 2 support is the best tested currently, but everything seems fine
  with views 3 as well.

Version 2

The new version of cache actions offers a lot of new features:

• Clearing The cache of more than one view at a time
• Clearing The cache of specific panel page variants
• Clearing The cache of specific panel page panes
• Clearing The cache of specific mini panel variants
• Clearing The cache of specific mini panel panes
• Unit tests

This module provides an alternative cache.inc file to serve anonymous page requests from xCache. This module makes use of DRUPAL_BOOTSTRAP_EARLY_PAGE_CACHE and implements page_cache_fastpath().

For anonymous users I want to serve pages from XCache, but I didnt want to use memory caching as a replacement for every cache table, only serving cache_page content for anon users from XCache.

Some of the code and concept is inspired by Cache Router, Memcache and XCache however for most parts the code is something I wrote in collaboration with Nick Thompson

The concept

- set a cookie for logged in users (anon/auth flag)
- page_cache_fastpath() checks if cookie is not set
- if cookie is set(auth user): proceed as normal, standard drupal cache functions (no cache)

- if cookie is not set (anon):
-- check if cached page exists in XCache, if it does serve the page
-- if cache doesnt exist in xcache, check db, exists in DB? save it in XCache & serve page
-- page doesnt exist in XCache or DB? Generate page, cache it in DB and Xcache, serve page

Standard menu tree editor consumes too much memory. Menu editor with about 1000 items reaches 64Mb memory limit.

The aim of the project is to create a system, based on services, which will make it possible to transparently use entities from a different site as local entities.

This module allows to browse comfortably and to be able to display slow queries for the current page using Devel module at the same time .
The slow query log is not displayed on initial page load but is stored in cache for a short period instead, so it then can be fetched in a separate AJAX request. Note that query summary is displayed same as before so user can make a comfortable decision whether he does need to read the log.