Performance

The MongoDB module suite for Drupal 10 stores data in MongoDB instead of the default Drupal SQL database.

For Drupal 11/10 site administrators

It means a faster Drupal and better logs, without a line of code.

• it provides a more usable user interface to access logs, and a faster database logging than core, without the complexities associated with external logging mechanisms like the Elastic Stack (BELK).
• it provides a faster implementation of the Drupal Key-Value store and Queue API
• overall, it provides a simple way to reduce the load on your SQL database server, without needing complex configuration or having to write a single line of code.

For Drupal 11/10 project developers

It means easy project development using MongoDB.

This module provides configurable actions upon events that will expire URLs from caches like reverse proxy caches, internal page caches, etc.This module make more sense when Minimum Cache Lifetime setting is set to a value other than none.

There is now integration with the following modules:

• Boost - deletes expired pages (files) from the file system.
• Varnish - integrates over an administrative socket.
• Fastly - Varnish/CDN caching
• Purge - expires urls by sending purge requests to Varnish, Squid and Nginx over HTTP.
• Acquia Purge - allows Drupal sites hosted on Acquia Cloud to automatically purge pages from their Varnish powered load balancers..
• Memcache Storage - allows to delete pages that were cached in a memcached instances.
• Akamai - provides an integration with the Akamai Cache Control Utility (CCU) Web Service
• Recacher - Page cache warmer.

Module's features may extend if next modules are enabled:

• Drush - provides drush commands to expire urls (xp-url), paths (xp-path), nodes (xp-node), users (xp-user), comments (xp-comment) from the command line shell and scripts.
• Rules - provides actions for the Rules module to allow more advanced cache expiration scenarios.
• Token - provides modal dialog with list of available tokens.
• References and Entity reference - module may expire referenced entities' urls.

This module aims to utilize Google Closure Compiler API/application to optimize your cached JavaScript files.

More info about the application/service:
http://code.google.com/closure/compiler/

Closure Compiler module looks at the cached JavaScript folder (sites/default/files/js) and processes files on cron run. It basically supports 3 different modes:

1) Compile locally via Java based compiler
2) Send JavaScript file contents to the API
3) Send JavaScript file paths to the API (Requires your site to be publicly accessible by Google)

Backport of Drupal 7 Queue API.

Note: if you use Drupal Queue, make sure to configure Drupal cron and Drupal Queue's own cron entry point. See README.txt for details.

Entity cache puts core entities into Drupal's cache API.

Due to the entity loading changes in Drupal 7, no core patches are required.

How to use it

This module has no user interface, if you enable it, entities will start being cached, if you disable it, they'll stop.

Supported core entities

• Nodes
• Comments
• Taxonomy terms
• Taxonomy vocabularies
• Files
• Users

Support for contrib entities:

There is no automated support for contrib entities, to use entitycache for a contrib or custom entity:

• Create a cache_entity_$myentity table/bin.
• Specify EntityCacheDefaultEntityController as your controller class in hook_entity_info(), or extend it.
• Never update your entity tables outside of save/delete API calls.

Tests

Entity cache is now set up for automated testing on Drupal.org, see current HEAD status.

This module is being developed for Drupal 7, and will never be backported to Drupal 6. For Drupal 6 you may want to look at this pressflow merge request or http://drupal.org/project/advcache.

If your talking about very very very fast file transfer then here is the destiny.

Why xsend module is made for?

xsend is a simple module to help you to speed up your private file transfers. Normally Drupal private file transfer is quite troublesome and not secure if the files folder is located at public_html. This module will also help protect your files from unauthorized access.

Why you need this?

• If you're still using Drupal public file transfer you're not secure at all. Every one can get your files.
• If you're using Drupal private file transfer, you're secure. But file transfer to the client is very slow.
• Fast secure file transfer can only be achieved from the xsend.

How to migrate to xsend?

• If you're using a standard Drupal installation then follow the instructions in the INSTALL file.
• If you're currently using private file transfer correctly, then you can still use this INSTALL guide, but make sure keep empty, the path to Drupal installation directory settings.

What is mod_xsendfile

mod_xsendfile is a small Apache2 module that processes X-SENDFILE headers registered by the original output handler.