TYPO3 Community Writer’s Guide
We’re excited to announce the launch of the Community Writer's Guide. This guide is designed to help anyone in the TYPO3 community create clear,…
Intended Audience
This article is intended for TYPO3 administrators who are considering client-side caching of content to improve performance.
You should be able to install and configure TYPO3 and know about the basics of TypoScript.
How it started
The Danish Consumer Agency runs the consumers' portal <link http: www.forbrug.dk _blank>forbrug.dk which is one of the largest TYPO3 installations in the world with 130,000 unique visitors giving 13 million hits per month.
This was managed with only 1 server for the website and database and 1 server for delivering mail. During the fall 2004 they experienced spikes in their traffic (usually caused by being mentioned on TV and net media). These spikes were more than the installation could handle.
Possible solutions
Upgrading the CPUs in the server was quickly ruled out as a solution: Doubling the speed would have cost at least 15,000 Euro in hardware alone.
So a software solution was needed. They analyzed their documents and most of them are not changed during 24 hours – these could be cached without any problems. A few, however, must never be cached as they change (e.g. the result of a search).
„We tried making a small change where all pages were cached for 24 hours using Apache's proxy module as caching engine. While this gave a remarkable speed up (in the order of 10 times) this proved fatal to the few pages that must never cached.
The right thing to do was of course to make TYPO3 compliant with current caching practices (e.g. RFC-2616). After identifying the changes needed in term of HTTP-headers that should be generated, we turned to Kasper Skårhøj and had him implement the changes. The identification process took in the order of a man week, and implementing the changes in TYPO3 and testing them took also in the order of a man week.“ (Ole Tange, www.forbrug.dk)
The page was cached by TYPO3
No *_INT or *_EXT objects were on the page (e.g. USER_INT)
No frontend user is logged in
No backend user is logged in
We’re excited to announce the launch of the Community Writer's Guide. This guide is designed to help anyone in the TYPO3 community create clear,…
The committee has expanded our international network and worked to strengthen TYPO3’s profile in developing markets. In these markets, TYPO3 is a…
The 22nd T3BOARD event will take place in Val di Fassa in Trentino from 11 March to 18 March 2023.
The version 11.5.22 of the TYPO3 Enterprise Content Management System has just been released.
PHP 8.2 was officially released on December 8, 2022. Our TYPO3 versions v11 LTS and v12 support the new PHP version already.
The versions 12.1.3, 11.5.21 and 10.4.34 of the TYPO3 Enterprise Content Management System have just been released.