Reuse Cached 404s

Drupal has a 404 caching problem.

Drupal's page cache is a fantastic and simple way to improve performance in production. If an anonymous user goes to http://yoursite.com/somepage twice, the second page load is a lot faster because Drupal doesn't spend time re-rendering it; it simply serves it from the cache.

But the problem is that pages are cached by their path. That means that the server has to do all the work to render the 404 page each time a new path is not found. This can be particularly noticeable if your 404 page is a node, view, or other rendered page.

This module takes over the caching process when a page is not found and makes it a little smarter. It's been tested with nodes, but it should work with any 404 page that is served through the menu system. It is compatible with multilingual sites. It caches the 404 once per language.

If you are already using Fast 404 (or Drupal 7's built-in version), you don't really need this module, and compatibility with those configurations hasn't been tested. It's a good alternative though when you need 404 pages with some dynamic content from your site and don't want to have to update HTML files when your site structure changes.

Installation

Cookie-Aware Page Cache

Cookie-Aware Page Cache module extends Drupal core's default database cache to key page cache entries by cookie in addition to URL.

You may need this if you are preparing different markup for pages depending on the value of a user's browser cookie, and the default database cache is the only caching mechanism available to you. For example, you may be displaying local information on a user's favorite store location, which is kept in a cookie. Or you might be using Context Breakpoint module, which uses a cookie to pass information about the user's screen size to use as a condition in the Context system.

You can specify more than one cookie to take into account when querying the page cache. However, you should only select cookies with limited sets of possible values. The performance benefits of page caching decrease as the number of possible cookie value combinations increases.

Image Property check

Features-
Reports all the images that exceed the maximum memory size limit of each image preset which results in the degradation of the performance of our website.
For now, the module is integrated with Performance and Scalability Checklist (pasc) module's checklist as there appears a tab which notifies user to configure the module. And also this module depends on pasc.
In future, the module may have its own checklist with some other performance enhancing criterias.
For Enhancements

Munin plugin pack

A collection of modules which implement munin plugin hooks. Track thing such as:

  • entity counts,
  • ping times,
  • curl times,
  • cache set and get times,
  • db access time,
  • and some other fun things.

Expire locale

Add locale and translation based expiration rules for absolute URLs when expiring and purging pages. Extending the Expire module.

watchdog_restrict

This small module restricts logging for messages with a severity lower than configured value.
To use it, install it as usual and go to admin/config/development/logging and select the mininal level to log.
All messages with a lower severity will not be sent to watchdog hooks (dblog, syslog, ...).

Pages

Subscribe with RSS Subscribe to RSS - Performance and Scalability