Performance and Scalability

The new 2.0-rc1 release is NOT backwards compatible with the previous version (not even with some 2.x-dev releases). If you're planning on using it, you should completely uninstall the previous version. Version 2.0 has gone through some serious refactoring and also comes with a MongoDB backend, which greatly improves performance on heavy-traffic sites.

Please note that the Drupal 6 version of this module is no longer supported. It is still available, but won't be developed any further.

What is Asynchronous Processing?

Asynchronous Processing is a module designed to call back ground process in Drupal.

What does it do?

The Asynchronous Processing will separate the Drupal task to mutil-process (as background process ).

It could be used for executing long-running tasks in the background, such as tasks involving significant network activity or encoding video, send an email etc.

Installation
1, Download & Copy this module to sites/all/modules folder.
2, Enable Asynchronous Processing modules

Native Drupal UI for XHProf. Work in progress…

Module maintainer @podarok
Drupal Firewall was implemented due huge data importing into commerce, ubercart, feeds and other modules
The main idea - disabling redundant hooks, functions and other procedures when doing background tasks (mostly via cron or custom page callback)
For that we use hook_module_implements_alter

Module config page (sometimes You have to know this address 8) ) admin/config/dfw/config

This module extends drupal to support http://www.cherokee-project.com/doc/modules_handlers_secdownload.html for private downloads. Urls generated for private ressources will expire after a certain time. The following transfer protocols are supported:

• Server (e.g. Cherokee)
• PHP
• X-Sendfile
• X-Accel-Redirect

This module provides a graph where you can see the size of the cache tables and labels marking some of the events that may empty the cache.

You can see how much damage those events do to your cache size.

The events recorded are:

• Cron run
• Insert, update, delete for:
• Nodes
• Users
• Taxonomy terms and vocabularies

More to come...

High performance integration with WinCache.

Project Has Moved

This project has moved here:
https://www.drupal.org/project/wincachedrupal

One Appliance to Rule Them All

Well, to make them play nice together anyway...

I was looking for a production/staging server build script or appliance that had LAMP, Webmin, Aegir, ISPConfig, and all the Drupal dependencies on top of a long term support (LTS) version of uBuntu.

On top of web and database services, I also wanted email and DNS, open source anti-spam and anti-virus, a firewall, and protection from DOS and other similar attacks. I also wanted all my admin interfaces to use SSL and I wanted secure SMTP enabled.

Basically, I wanted the offspring of a debaucherous affair between Webmin, Aegir, a slightly hardened LAMP, ISPConfig, and Drupal. I wanted - WALID.

Meet WALID. It's that genetically engineered super offspring.

WALID's the output of a build script that smaller-scale Drupal developers can use to quickly build a production server on a Cloud or Dedicated VPS (or download as an appliance). For Drupal developers that need more than shared hosting but aren't experienced in building or maintaining Linux servers, this will get you going. For developers who have reached a certain level in their Drupal-fu but who aren't experienced with Linux, WALID is a relatively secure and stable Drupal-centric production environment that can be managed via secure web interfaces by even non-Linux pros. [This is the goal anyway...]

The Materialized Views system originally written by David Strauss for Drupal.org and being extended for Drupal 7 and Views as a Google Summer of Code project.

This module uses the batch API for building the Drupal menu routers and links.

It provides a link for building the menu without need to process the modules page.

It also overwrites the submission of the form found in the admin/build/modules page.

Rather than processing everything at once, the menu is built apart from theme registry and such things.

This is really useful if you can't increase your PHP memory limit.

So, if your project has a lot of menu callbacks, you usually get a memory overflow when you try to build the menu.