Performance

Developers should check also the AWS SDK for PHP module instead.
This module doesn't use the Library API, it is recommended to use creeper if the only library that your project will use is the AWS SDK for PHP.

------------------------------------------------------------------------------

The creeper project provide a AWS SDK for PHP (previously named Tarzan and Cloudfusion) integration module for Drupal. the AWS SDK for PHP is in my opinion the best PHP library to work with Amazon web services. It covers every aspect of Amazon Web Services:

• Simple storage service - S3
• Elastic compute cloud - EC2
• SimpleDB - SDB
• Simple Email Service - SES
• Amazon Product Advertising Service - PAS
• Simple Queue Service - SQS
• Cloudfront, the amazon CDN based on S3
• Amazon Associates Web Service - AAWS

Once installed this module allow you to use the powerful AWS SDK for PHP API in any other module; you just have to declare a dependencie to the creeper module in the .info file.

This module provides an easy way to import previously exported Views definitions.

CloudFront module integrates with imagecache to serve dynamic images from the Amazon CloudFront CDN. Dynamic images are placed in a queue and served immediately from the local filesystem.

CSS Gzip will no longer be updated/supported and is considered obsolete. All future development is being done in the Advanced CSS/JS Aggregation module.

Compound Eye assists Drupal system administrators who wish to monitor the status of several Drupal installations at once. It consists of a server module and a client module.

The Authcache module offers page caching for both anonymous users and logged-in authenticated users. This allows Drupal/PHP to only spend 1-2 milliseconds serving pages, greatly reducing server resources.

Please note that enabling authenticated user caching will require modifying how your user-customized content displays on your pages. You should be an experienced Drupal developer if you choose to implement the full functionality of this module.

How does it work?

Authcache saves the final rendered HTML of a page to serve visitors. A separate cache is created for each user role as defined by the administrator, so some roles can be excluded if necessary.

Authcache places priority on serving pages to the visitor as fast as possible. After a page is loaded by the browser, a second HTTP request may be performed via Ajax. This initiates a lightweight DRUPAL_BOOTSTRAP_SESSION that allows SQL queries to be executed (such as updating the user "history" table or node "statistics" table), and returns any user-customized data to the page (such as form tokens or default values on a contact form).