Performance

This module provides graphical dashboard generated from RRD data. The dashboards give administrator a quick overview of the performance on their physical server.

This module acts like an abstraction layer for different query builders or content list functionalities in Drupal. This abstraction layer makes it possible to display and cache lists of entities in a consistent way through Panels. The integration with Cache Tags the friendly fork of Cache Tags allows for very granular and effective cache invalidation for all your panes and entity lists.

Handler are provided for the following query builders or content list functionalities:

• Views
• Nodequeue
• Relation
• Entity Reference
• EntityFieldQuery

Why?

Views is great. It's the best thing that ever happened to Drupal! We are using Views for many things, but sometimes we just want to...

• ...display nodes directly from a Nodequeue, instead of doing it through Views

Drupal often add a lot of CSS and JS files to a page request. The added weight and number of HTTP requests is bad for performance. This can be partly fixed by the CSS and JS aggregation feature in Drupal (also see Aggregate cache). But you still have a slight weight problem to those aggregated files.

One solution is to avoid including unnecessary files in the first place. This module makes it easier for themes to specify what CSS and JS files to blacklist or whitelist. This is done from the themes .info file.

Example

What one often ends up with is a whitelist of CSS files and a blacklist of JS files. Consider the following example:

blacklist[scripts][] = "*/panels/js/panels.js"

whitelist[stylesheets][] = "*/system/system.base.css"
whitelist[stylesheets][] = "*/system/system.messages.css"

The setup above will blacklist panels.js (since it's only dealing with admin links which one might not use). And since we created a whitelist for CSS files, only specified files will be added to pages, thus only allowing system.base.css and system.messages.css in the example above.

Provides a queue backend for the Redis key-value store.

This module provides a hash-based cache for Panels and other Chaos Tools powered displays.

This support caching based on any combination of:

• Contexts (node, term, user etc)
• Arguments
• Drupal Path (args) (same as the Panels Page Cache Module)
• Full URL (including domain and query string)
• Users
• Roles

It also supports "simple" caching. If you would like to see it cache based on something I haven't thought of yet, open-up a feature request and I will likely add it.

The main advantage to using a hash-based cache is that the cache is automatically expired* when any of these items change. This means that you get automatic and instant refreshes of your cached item when your node , user, or term (or what-have-you) is updated. This means that you can more aggressively set your TTL on your caches, knowing that they will automatically be updated and thereby achieving a much higher hit ratio.

The other advantage is that you can cache based on the combination of *any* of the above items. Want your cache to be updated when either the context *or* the user's role changes? No problem!

Need a fast storage for your logs?