Without any effort on your part, MCMS already caches a whole bunch of stuff. This caching is probably enough for most websites. We'll go over the default caching features, and in the next section we'll see what you can do to enhance your website with custom ASP.NET output caching.
When a visitor to your MCMS website accesses a page, ASP.NET receives the request (or ASP if you are working with legacy templates), accesses the content, and compiles it in RAM, combining it with your template code (from the file-system) and any posting-specific MCMS content (such as placeholder content). Local attachments and resource gallery items used within postings are not saved in RAM but instead saved in the MCMS disk cache.
The disk cache for MCMS is contained in the /NR/rdonlyres/
virtual directory. Embedded resource gallery items and local attachments (JPGs, GIFs, DOCs, PDFs, etc.) are copied here from the database the first time they are accessed, and if the...