Performance

The Akamai modules provides integration with the Akamai Content Control Utility (CCU) Web Service.

Context HTTP Headers provides a set of Context reactions that allow you to set HTTP Response Headers for each context on your site.

Drupal 8+

A Drupal 8+ version of this module is in active development, a relatively stable beta version is available.
The Drupal 8+ version has been completely re-written and no longer provides an image toolkit. Optimizations are now defined as 'pipelines' that can be applied to images in various ways.
The module has built in support for core Image styles and a service allowing use in third party modules.

The module has been split into several other projects for easier maintainability and more modular installing. At least one or more processor module needs to be installed for the optimization to work.

• Image Optimize Binaries (for binaries locally installed on the server)
• Image Optimize reSmush.it
• Image Optimize TinyPNG
• ImageAPI Optimize GD for adjust compression quality per style
• Kraken
• ImageAPI Optimize AVIF & WebP
• ImageAPI Optimize WebP
• ImageAPI Optimize AVIF

Open Drupal 8 issues | All issues from all subprojects

Drupal 7

This is a toolkit for ImageAPI. It requires imageapi_gd or imageapi_imagemagick or any ImageAPI toolkit to work.

ImageAPI Optimize allows you to use your preferred toolkit and optimize (losslessly) the image when it is saved. Practice for web performance suggests that images should be optimized for better loading time. With this module enabled, Google's Page Speed will always give you an A in image optimize.

This small module is designed to help you performance-optimize your use of input filters and input formats.

D7 version now available.

Filter Check does the following:

• Shows which individual input filters cannot be cached by marking them with an asterisk on the format configuration page.
• Shows which input formats cannot be cached by appending an asterisk to their names.

How is this useful?

An input format consists of one or more input filters applied consecutively. The text you input (for example the body of a node) is usually processed by several input filters - those that are enabled in the format that you selected when you input the text. This processing may take significant time, which is why Drupal tries to cache the result so that the processing does not need to be repeated unnecessarily.

However, the output from some filters cannot be reliably cached (the PHP evaluator is an example.) Using such a non-cacheable filter prevents caching for all text which uses that format whether or not the functionality provided by the non-cacheable filter is actually needed. Clearly it makes good sense to avoid using a non-cacheable filter format unless it's really necessary.

Wondering why your views run so slow? Why after switching to InnoDB, MySQL isn't running any better? This module has the answers!

Indexes

It will show what CCK columns get used in a view filter or relationship and give you the option to add an index on it so the views query will run faster. Also can add indexes to core modules that could use one.

Engine

Ability to convert your database from MyISAM to InnoDB in order to eliminate table locks on data writes.

Collation

Are half your tables latin1_swedish_ci and the other half utf8_general_ci? Use this to change them all to utf8_general_ci.

MySQL Tuner

Have you never edited your my.conf file? This will give you hints at what values to tweak in order to get MySQL running better. Special thanks to MySQL Tuner, since this part of the module is a port of that project.

Future Plans:

• Figure out which experimental indexes are good & which ones are bad
• #798756: Better index suggestions with filters and sorts. Manage Multi Column Indexes
• #799230: Run explain on every views query
• #799236: Run explain on every query in the slow query log
• #817688: Engine Selection Per Table; Suggest you put site into maintenance mode

Similar Projects

MySQL Report
Shadow - SQL queries / views optimization
Materialized View API

This module allows you to profile your Drupal application using the XHProf profiler, Tideways and uprofiler (PHP 5 only)

Use community documentation to install/enable required PHP extension

XHProf is a hierarchical profiler for PHP. It reports function-level call counts and inclusive and exclusive metrics such as wall (elapsed) time, CPU time and memory usage. A function's profile can be broken down by callers or callees. The raw data collection component is implemented in C as a PHP Zend extension called xhprof. XHProf has a simple HTML based user interface (written in PHP). The browser based UI for viewing profiler results makes it easy to view results or to share results with peers. A callgraph image view is also supported.

It also provides a native Drupal UI (as opposed to facebook's original php front end) to view the profiling data. Having this in Drupal provides several advantages:

• Simpler setup
• No need to setup extra vhosts
• Limit access via roles and permissions
• Use alternative storage backends such as MongoDb

D8+ version also supports:

• Profilers: XHProf, Tideways and uprofiler (PHP 5 only).
• Append --xh-link and Drush 8 will save a profile to the same directory that this module uses. Browse Drush 8 profile data with this module.