Movable Type offers a number of features to help administrators increase the performance of their system. Chief among them is template module caching. As the name may imply, any template module in Movable Type can have caching enabled, which causes Movable Type to store the output and HTML from the module in Movable Type's database for later use. That way, if a template module is used frequently, then Movable Type will minimize the number of times it goes to the database to generate its content.
To help our users take complete advantage of this important feature introduced in Movable Type 4.2, we have assembled the "Ultimate Guide to Template Module Caching." It comes complete with:
- insight into why this feature can have such profound performance benefits
- sample code
- tips on what to look for when decided which modules to cache
- a detailed explanation of how this feature can be used in conjunction with server side includes
- information you may not have known about, like the ability to override the global cache context and create more granular and context sensitive module caches
We hope to make this guide the most definitive source for information about this feature, so if you have additions or ideas for how to make Ultimate Guide to Template Module Caching better, please let us know by leaving us a comment.
Leave a comment
Have a question, please use the MT Forums. Notes sumbitted here should pertain to tips & hints regarding documentation. Your note may be removed once it's contents has be integrated into the body of the page.