rp7's sandbox: Entity cache Warmer

This module is designed to work in conjunction with the Entitycache module. By default, entities are cached when loaded. This module pro-actively puts entities into the entity cache, resulting in a faster user experience.

• The module does this in a smart way, by keeping track which entities are already cached and which not.
• The type of entities you want to warm up the entity cache for, can be configured through the interface.
• A drush command is available to warm up the entity cache for one or more entity types. One can choose to warm up all entities at once, or a given amount of entities.
• The entity cache can be warmed up through cron. Elysia cron is also supported (per entity type).

For the advanced users:

• Hooks can be implemented in order to prioritize specific entities (eg. most recent nodes should be handled first).
• Various processes within Drupal may trigger a full entity cache wipe for one or more entity types. To give more insight on this matter, a debug functionality is provided.

About Drush Entity Cache Loader
Altough the end-goal is the same, the way Drush Entity Cache Loader module (https://drupal.org/project/drush_ecl) works is substantially different. While Drush Entity Cache Loader is a nice module, it's merely a Drush command launching a batch process putting all entities of one or more entity types into the entity cache. The Entity cache Warmer module

• does not needlessly process entities already in the entity cache
• can either warm up all remaining entities at once, or a subset (eg. 100 entities per cron run)
• is configurable through the interface
• can be used through either cron, interface or drush
• can prioritize entities based on specific use cases