Performance

This module is abandoned due to a security issue the maintainer never fixed. See SA-2012-006 for details.

If you want to use this module, your options are:

• Work on the issue in this module's queue to fix the bug which includes contribution from the module maintainer and others
• Choose another module instead
• Fix the module and then contact the security team to have your version reviewed and the project handed over to you following the abandoned project process
• Hire someone to fix the security bug so the module can be re-published (see this guide on how to hire a Drupal site developer)

SuperCron is a complete replacement for Drupal's built-in Cron functionality. It allows you to:

1. See the list of all Cron hooks found in the enabled modules
2. Change the order in which cron hooks are called
3. Disable certain hooks

The no_anon module eliminates the need for sessions for anonymous users

This has the potential to reduce the server load and/or database contention on busy sites, since crawlers do not create entries in the session table for every page view.

See how this positively affected a large site at reducing server load by eliminating anonymous sessions for Drupal 6.x.

Side effects

Some modules use the $_SESSION superglobal variable to store info for anonymous users will be affected by this module. If your modules use this only for logged in users, then it will not be an issue. Before you install this module, make sure that your modules do not depend on that.

This approach is known to cause the following features not to work:

1. The core Who's Online block

2. The core Throttle module

3. The anonymous user count in the Administration Menu module.

4. OpenID (see #873024: Core openid module also affected for more details.

For installation instructions, please refer to the README.txt file included with the tar ball.

Note that this module is for Drupal 6.x only. Drupal 7.x already has a similar feature in core.

Author

Khalid Baheyeldin of 2bits.com.

Experimental cache module for Drupal core modules, which work for anonymous and logged users as well.
It will increase your performance even 2x on very heavy websites, when other caches are useless.
It's not a standard cache engine, so you can mix it with other cache engines as well.
No need to change your settings.php file.

NOTE

It's not ready for production servers yet.
Requirements to see some improvements: probably around more than 100 activated modules
Please use it only for testing purposes.
See some benchmarking statistics here:
#471322: Initial test

REQUIREMENTS

Probably you need at least more than 100 activated modules.
Nobody using cache engine, if website is loading fast.
If you have problem with performance, then install this module.
Please use it for testing purposes, because it could cause some side effects.
Later it should become more stable.

INSTALLATION

- Just enable the module;)

TROUBLESHOOTING

This module changing system and menu_router core tables to run cache engine and it's not stable yet, so in case when your experience WSOD - please execute WSOD from DTools module (emergency mode) to fix common WSOD issues.
If you are not experienced user, please do not install this module to prevent any damage of your website.

CACHING METHODS

Project merged into Drupal Tweaks module

Please use following module instead:
Drupal Tweaks

It's a powerful module which enhance other modules functionality by personalizing form settings provided by them per user or per role.

An API for browsing next/previous nodes without overloading your database server.

Description

This module allows you to know the previous or next nodes for any given node. This is very useful for providing navigational links to the user without the expensive queries required to dynamically deduce such information on the fly.

The use case is two fold:

Usability/Navigation

For example, on a site with a gallery of images, you want to show a next/previous link with a thumbnail under each image. Your site's visitor click on the link to show new content or browse it.

Scalability

Although the previous and next nodes can be deduced with some SQL work, the queries to do so are very heavy on the database, and can bring a site to its knees. This module solves this problem by storing the previous/next node in a table so lookups are fast. Once the module is installed, it will build this index backwards via cron until all nodes have been indexed. See the "More Info" section below for a detailed post on the positive scalability impacts of implementing this module.

Configuration

The module can be restricted to certain content types to be included in the previous/next indexing. For example, you want the site's visitors to browse through video and image nodes only, but not blogs and regular pages.