Performance and Scalability

This plugin ensures that your Drupal website runs optimally when using Incapsula

By using this plugin you will have no change to your originating IPs when using Incapsula. Incapsula acts as a reverse proxy and all incoming connections to your website first pass through one of Incapsula's servers. This plugin will ensure that you continue to see the real originating IP of your website visitors.

The plugin is **highly recommended** for Joomla users using the Incapsula service.

HOW IT WORKS:

Integration of the spriteme.js of spriteme.org

The Ultimate Cron handling for Drupal.
Runs cron jobs individually in parallel using configurable rules, pool management and load balancing.

2.5 READY!

Ultimate Cron 7.x-2.5 is out now.
Ultimate Cron 1.x documentation can be found at https://drupal.org/node/1666944

The old project page for Ultimate Cron 1.x can be found at https://drupal.org/node/2195381

Changes

• No more dependecy to Background Process. Ultimate Cron now works without Background Process. However, Background Process is still supported for true parallelism
• Refactored to use cTools plugins, making it easier to extend Ultimate Cron.
• Now includes the daemonizer and queue throttling features, previously found in the modules Ultimate Cron Daemonizer and Ultimate Cron Queue Scaler
• Hopefully a more robust lock and logging mechanism.
• Integration with nodejs for live update on cron page
• Nagios support has not been re-implemented

Upgrade path from 7.x-1.x and previous

• Add and enable Chaos tool suite (ctools) before upgrading Ultimate Cron (not just before running update.php but even before upgrading the code).
• Disable cron while upgrading.
• Existing db-stored settings will be upgraded.
• Existing features containing Ultimate Cron settings will be stored in db, for easier re-export.
• Existing log table will be modified. Beware, that if the table contains many entries, the upgrade may take some time.

Plugins

Ultimate Cron is built upon 4 plugin types.

• Settings: - plugins that provide custom settings for jobs (bundled: general, queue).
• Schedulers: - plugins that provide a mechanism for whether or not a job should run at a certain time (bundled: simple, crontab).
• Launchers: - plugins that provide a way of launching jobs (bundled: serial, background_process).
• Loggers: - plugins that provide a logging backing for job status (bundled: database, cache).

Ultimate Cron 7.x-2.x documentation can be found at https://drupal.org/node/2195383

Features

• Works out-of-the box in most cases (or aims to)
• Parallel exection of cron jobs
• Configuration per job (enable/disable, rules, etc.)
• Multiple rules per cron job
• Pool management and load balancing using Background process
• Support for Drupal Queues
• Overview of cron jobs
• Log history of cron jobs
• Status/error messages per cron job, providing easy debugging of troublesome cron jobs
• Uses hook_cronapi() (Elysia Cron compatible, NOT 2.x, please use hook_cron_alter() for similar functionality)
• hook_cron_alter() for easy adding/manipulating cron jobs
• Poormans cron with keepalive a granularity of 1 minute
• Drush support (list, start, enable/disable jobs from the command line)

This module uses Queue to rebuild node access in a non-disruptive
manner. This module depends on drupal_queue.

Node Access Rebuild Process

En-queueing process:

1. On cron, module checks if node access needs rebuild.
2. All nodes are queued for rebuild.
3. Node access needs rebuild variable is reset.

Queue processing:

1. A node (X) is claimed from the queue.
2. Node X's node access records are deleted.
3. Node X's node access records are rebuilt.
4. Node X's queue entry is deleted.

Checklist system for launching Drupal websites to a production environment.
This module runs a series of tests to check your site configuration allowing you to optimize and secure your site for public consumption.

This module provides a PSR-0 compatible autoloader. It can be also used as a map-based autoloader. This autoloader support different folders for different namespaces, can be used for anything, external libraries but PSR-0 compatible modules code also.

It can be used in pre-bootstrap early code, even before Drupal has been bootstrapped itself (with the help of the settings.php file) or included with your cache, session or lock backends, therefore enabling it on really early bootstrap phases.

Session proxy is not a module: it is a replacement for Drupal core session handling API.

It acts as a proxy between fixed core procedural API towards a fully object oriented, more flexible and easier to extend session management API.

Basically, it strongly encapsulate the original API, separating user management against raw session storage: by using it you are able to implement any session storage engine (memcache, redis, ... ) without handling cookies and by users yourself.

In order to perform a "rush" performance test you will need to allow the app to hit a URL on your site and return only "42" for verification. This will let you set that URL which is custom to your account and setup the simple response... if you don't want txt files in your root :)

Blitz makes load and performance testing fun.

Visit blitz.io to create an account.

Turns out this module isn't very needed...

This is a library module. It provides no out of the box functionality other then providing an API that other modules/code can use. Other projects might require/recommend this module. Install HTTPRL only if other modules recommend or require it.

The module allows to build high performance tracker replacement using Views module. It's based on ideas from the Tracker 2 project, but is almost a complete rewrite.