Caching of menus and blocks in xml can reduce a large no of queries from db.

When a user opens site, an xml cache is created for the menus and blocks (all the menus and block settings for guest users) will be cached. So when user goes to another page menus and block will populated from xml cache files. It will reduce large amount of load from server. Less no of queries will be executed for every page load.

When user login then xml cache files will be updated according user's role.

-----
Sharique uddin Ahmed Farooqui
IT head, Managefolio.com

Comments

mdixoncm’s picture

Their is a module to handle the caching of blocks (http://drupal.org/project/blockcache), and the actual building of the menu doesn't require any db hits (it simply creates a big old array) - you might be thinking of the url function, which needs to hit the DB to see check aliased paths - and IIRC these are cached already?

There are numerous projects around that have attempted to implement file based (or memory based, using things like memcache) caching - although I think they all require some patches to the Drupal core.

Like books? Check out booktribes the new (Drupal based) community for book lovers
from Computerminds