Performance

Elysia Cron extends Drupal standard cron, allowing a fine grain control over each task and several ways to add custom cron jobs to your site.

• Set the timings and frequencies of each cron task (you can run some jobs every day at a specified hour, other only monthly and so on...). For each task you can simply choose between some frequently used options ("once a day", "once a month" ...), or use a powerful "linux crontab"-like syntax to set the accurate timings. You can even define your frequently used options to speed up site configuration.
• Parallel execution of cron task: you can group jobs in channels and execute then simultaneously: so a task that takes a lot of time to execute won't block other tasks that need to be executed every 5 minutes...
• You can disable all tasks, an entire channel or a single task.
• Change the priority/order of task execution.
• Manual force the execution of a cron tasks.
• Detailed overview of cron status with time statistics for single tasks and channels.
• powerful API for module developers: you can define extra cron tasks for your modules, each one with own default timings (site administrators can override them by configuration, other modules via hook_alter).
• Administrators can define custom jobs (call to functions with parameters), via the "script" option.
• Several optimization for frequent cron calls and error handling.
• Protection from external cron calling by cron_key or allowed host list.

Elysia has no dependencies with contributed modules, and doesn't need to patch the core: it can be used in minimal Drupal installation with only core modules.

3rd party integration:

• Ping feature, for external tracking services like host-tracker to tell whether cron is functioning properly on your site.
• Drush support: you can call "drush elysia-cron run" to manually run extended cron.
• CTools support for exports/backup of task settings.
• Features support.

Overview

JS Callback Handler is a solution for creating highly performant server requests. This includes, but is not limited to, creating simple JSON callbacks.

This API is intended for module developers who wish to provide more of a "lean" approach to the Drupal bootstrapping process (not the front-end framework).

Note: this API does nothing by itself. It requires other modules to leverage its functionality and APIs.

About

CacheRouter is a caching system for Drupal allowing you to assign individual cache tables to specific cache technology. CacheRouter has an option to utilize the page_fast_cache part of Drupal in order to reduce the amount of resources needed for serving pages to anonymous users.

Drush integration #642544-12: Weird thing. Keeps happening.

NO DRUPAL 7 VERSION OF THIS MODULE WILL BE RELEASED. See #593238: Do not release Drupal 7 version of this and move the engines into separate projects for details.

Cache Router supports the following technologies natively:

• APC
• Database
• eAccelerator
• File
• Memcache
• Memcached (Alpha)
• XCache

Tutorial of Alpha 4 in action
HTML Export allows you to take your Drupal site and select paths from it based on criteria to export to HTML. It supports OG, results from Views, per content type, all menu router items, and all nodes as default criteria for publishing to html. Developers can extend and override these selections through a simple hook / api system. This module requires that Simple HTML Dom module/library be installed to help with the parsing of the html being created.

Drupal 6.x-2.x

Special note: The Base URL ($base_url) MUST be set in your site's settings.php file in order to use this module.

Features

• API hooks able to add / define / prune / alter the paths, assets, and html data used in export
• Supports ANY drupal path, not just nodes
• Ability to remove DOM elements in bulk during page export (follows convention div[id=admin-toolbar] to remove admin module output)
• New publishing metric to make creation cleaner (folder stacking instead of flat nodes)
• Batch API to avoid timeouts and be able to handle massive sites
• Selection criteria hooked in through API
• Selection criteria hooked up to views queries

MailQ is a module that queues ALL mails originating from a Drupal site into a queue and then processes this queue and sends mails in batches during cron runs. However, it still uses drupal core or other modules like Mimemail to actually send the mails.

Update: A new release 6.x-2.0-alpha1 is now available. Download and try.

This module is a set of base component and connectors to integrate Doctrine ORM with Drupal Core. The Doctrine Object Relational Mapper sits on top of a powerful database abstraction layer (DBAL). One of its key features is the option to write database queries in a proprietary object oriented SQL dialect called Doctrine Query Language (DQL), inspired by Hibernates HQL.

http://www.doctrine-project.org/projects/orm.html

This module provides integration with Doctrine ORM, giving developers a powerful alternative to SQL that maintains flexibility without requiring unnecessary code duplication.

Designed with a few goal in mind:

• Maintainability: the software will evolves with the Doctrine library and with versions of Drupal, the code base is written to cope with a changed environment. Test suit is the same quality as the software itself, allowing the isolation of defect for further correction and ensure new requirements will not break anything, thus, making future maintenance easier.
• Dependability: it does what it claims, and is trustworthy. The code is optimized to run for limited resources computers with special care to cache optimizations or any form of I/O which are costly.