Shine

Creates a Memory File system to store assets. i.e. Aggregated CSS/JS files. Shine can be used to distribute assets across a multiple server architecture.
Shine is powered by jsmin-php https://github.com/rgrove/jsmin-php/

dba KV/cache

Implements a cache class based on http://en.wikipedia.org/wiki/Berkeley_DB

Thanks @miro_dietiker for the idea

Rules Image Styles

The prupose of this module is to pre-generate styles via rules.

DO NOT USE THIS IN PRODUCTION. THIS IS AN EXPERIMENTAL MODULE.

Why

Normally the image derivates get created on request. But what if you want to display informations on presets, without displaying them. Like a download link with an info on size, resolution...then the image must already exist.

Downloads

xsendfile

Home of xsendfile integration for nginx and apache.
Merged Apache functionality with: http://drupal.org/project/nginx_accel_redirect

Downloads

Menuperformance

Drupal's regular menu system administration doesn't scale very well. This is due to the fact that for all node edit pages, node type edit pages and vocabulary edit pages (when Taxonomy Menu is active), Drupal loads all menu items from all menus in the system. For large amount of menu items, this slows down the system to an unusably slow speed, or even causes timeouts.

This is a known problem in Drupal core. This comment is from the menu module:

  // The menu_links table can be practically any size and we need a way to
  // allow contrib modules to provide more scalable pattern choosers.
  // hook_form_alter is too late in itself because all the possible parents are
  // retrieved here, unless menu_override_parent_selector is set to TRUE.
  if (variable_get('menu_override_parent_selector', FALSE)) {
    return array();
  }

Menuperformance takes advantage of this, and sets the variable when installed. It then proceeds to add its own AJAX based parent menu item selector widgets for the node edit, node type edit and vocabulary edit pages.

Dependencies

None.

Documentation

Downloads

HTTP cache

Proof-of-concept module providing HTTP caching for authenticated users.

How it works

By default any response - currently only pages rendered through drupal_render_page() - may be cached locally by the user agent, except if explicitly set not to (e.g. certain paths, or if the page contains dynamic content that changes every request). Along each cacheable response an ETag HTTP header is passed containing identifiers of all displayed data (entities, etc).

Pages

Subscribe with RSS Subscribe to RSS - Performance and Scalability