Performance

The Cleaner module allows the admin to set a schedule for clearing caches, watchdog, and old sessions.

Seeking Co-Maintainer, please apply in the issue queue if interested

• Part 1 - http://bit.ly/PGu8J
• Part 2 - http://bit.ly/yR6Zy
• Part 3 - http://bit.ly/BLWrU
• Network Modules Feature walk through - http://bit.ly/cW4q3
• Network Watchdog Feature - http://bit.ly/17UUyA

This module will allow you to manage a vast number of sites from one Drupal site. The purpose of this project is aggregation of information and link generation to help you accomplish common tasks faster. In case you're concerned, there is no permission escalation going on because you still have to click to access the other sites pages to set the settings you want. This is merely aggregating information for you at the moment. In the future it will allow for modifying settings across the network (hopefully) but is stil a ways off. Here's what you get in this module and will get in the future:

What's there now:

• Network Status Report -- Spend minutes and hours going between status pages on your the sites in your infrastructure making sure you don't have any database updates to run or cron jobs? This is part of what this will solve (v 1.0)

Ajaxify Regions attempts to handle the problem of serving cached content for authenticated users.

Upgrade to the CDN module!

The Parallel module is now obsolete. The final version (1.0) doesn't do anything anymore, it simply migrates all settings to the CDN module when you run update.php. When you uninstall the Parallel module, all of Parallel's settings are deleted.
The CDN module contains a superset of the Parallel module's functionality, with a better UI, and a Drupal 7 port readily available.
The migration path is provided and is documented in the CDN module's UPGRADE.txt file. Also see the Parallel 1.0 release notes!

Below you, can find a quick tutorial on how you can duplicate the Parallel module's behavior using the CDN module.

Setup:

1. Create 3 new subdomains that point to your main domain (using "CNAME" DNS records). If your main domain is
   example.com, then create
   • css.example.com
   • js.example.com
   • img.example.com
2. Install & enable the CDN module module.
3. Go to admin/settings/cdn/details (Drupal 6) or admin/config/development/cdn/details (Drupal 7) and enter the following CDN mapping:
   
http://css.example.com|.css
http://js.example.com|.js

This module provides integration between your Drupal site and Varnish cache, an advanced and very fast reverse-proxy system.

This module is for experienced users only. It requires manual configuration of settings.php and maybe also the database and the ability to set up and user subdomains