TYPO3 offers a caching mechanism. A glance at the operating mode of CM systems tells you how important this is. Except for static pages, most CMSs generate their contents from a database. With a high number of visitors, the page slows down considerably. To prevent this, the page is put into an intermediate storage position in the form of HTML code. If visitors call the page again, it is not composed afresh from the individual components of the database—the page already generated is displayed from the cache.
TYPO3 undertakes the caching of pages itself. But as soon as changes are made in the page, the cache is automatically deleted.
Configuration settings, the HTML output of static pages, and picture sizes are the main items cached in TYPO3. Extensions also make use of the caching function in order to maximize output speed. Some elements do not use the cache even though it is commonly assumed that they do. Among these are pictures created on the server.
Now that...