Back in Chapter 1, we saw how MCMS renders content. MCMS does not produce static HTML pages anywhere on the server's hard disk, even though when you view the source of an MCMS posting in your browser you will see plain HTML. MCMS assembles this HTML for postings on the fly from template files and content in embedded MCMS placeholders. While dynamically generating pages ensures flexibility in the design of the application, it incurs processing overheads. More time is taken to generate and deliver dynamic pages as compared with static pages, which are delivered without any processing by the server.
MCMS optimizes site performance with four caching mechanisms:
Disk cache. When accessed for the first time, MCMS resource gallery items and local attachments are pulled from the database and stored on disk in the MCMS disk cache. Subsequent requests for cached resources can then be pulled from the disk cache instead of rebuilding them from the database.
Node cache. When...