Performance

What does this module do?

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

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

jStats allows you to aggregate statistics about visitors on your site, without breaking the cache-ability of your pages.

At its core, jStats could be seen as a bridge between the core Statistics module, that stores its data in Drupal but is incompatible with aggressive and external caching, and Google Analytics, that only adds a small JS fragment to the page and thus makes them perfectly cachable, but can't easily be accessed by Drupal modules (in order for example to sort a listing of node by the number of node views): it's a lightweight way to keep your statistic data in your database, that still works when the page you want to have statistics on is stored in cache.

[NOTE: This module has been deprecated as of June 2013 in favor of Cache Expiration. If you're currently using Boost Expire, please follow these directions to switch from Boost Expire to Cache Expiration on your site!]

A cache expiration module to go with Boost for Drupal 7.

Currently, Boost for Drupal 7 doesn't do any active cache expiration (see #1069438: How to Flush Boost Cache in Drupal 7.x), and this means that when you update a node, post a comment, etc., Boost will continue serving stale content from its static HTML cache until the file is finally cleaned up on a cron run.

For many sites, especially smaller sites where content is updated infrequently and cron may be run hourly or even less frequently, this means stale content will be served for quite some time, unless someone visits the Performance page and clears all the site's caches manually.

This module alleviates that problem by simply flushing Boost's static HTML cache every time a node or comment is posted or updated. You can set the module to respect your site's Minimum cache lifetime so it doesn't flush the cache until the minimum lifetime has passed.

This module may become deprecated in favor of a more universal solution (like Boost integration with the Cache Expiration module).

In brief, this project could help you rewrite the URLs.

1. sub urls of node and user will be rewritten when the parent url has an alias.
2. you can use regex to rewrite any url if you want

NOTICE: no need to enable this module, just include the core in your settings.php

In Drupal, we have node and user. In many cases, node|user has many sub-tab menu, such as node/%/info node/%/devel and any other MENU_LOCAL_TASK.
If you use url_alias, you need to add alias for each of them. This module, Rewrite Sub Link, will help you rewrite them automatically, and which doesn't user url_alias, so when you have millions of node, it won't case a performance issue.

Additionally, this module support regular express, so you can write your regular express to change your URL.

Light-weight Usage
add this line in the settings.php file,
include_once "sites/all/modules/contrib/rewrite_sub_link/rewrite_sub_link.core.inc";
add your custom settings in your settings.php
include_once "path_to_your_custom_rewrite_settings.php"
or change the code in rewrite_sub_link/rewrite_settings.php directly.

then all the sub links of user and node will be rewritten automatically.
Please check rewrite_settings.php file and change for your custom settings.

NOTICE