You should know who caches what and how to cache it. There are so many aspects to consider. Bottomline: You need to know your system and what you are doing!
4. Caching in a nutshell
• Caching is bad
• Not caching is even worse
• Clearing your caches is a workaround
• Clear your caches - or... know what you're doing
8. Why should we cache
• Serve data faster that other needs lot of
processing, memory, IO
• Saves the environment! Saves lives!
• Main issue: Get it under control
17. Things can change
• Clear your browser cache?
• Not the problem in the first place
• Ensure that your browser knows what to cache
18. Things can change
• Just add the tstamp so the browser caches
different variants
<link rel="stylesheet" type="text/css"
href="/typo3conf/ext/site_for_drevil/Resources/
Public/Css/main.css?1499248117">
22. TYPO3 Cache - First Hit
Request /products/pampers/
Response
Heavy lifting
23. TYPO3 Cache - Second Hit
Request /products/pampers/
Response
Done here
24. About cHash
• Variant of the page that gets a separate cache
entry
• Depends on the additional GET variants
• Some parameters can be excluded in TYPO3
34. Lessons learned
• Fix the issue, not the symptom
• Save the environment
• Don't cache forever, it will bite you
• Know your system, what it does
• Never use no_cache=1
35. Go and save goats
... and don't forget to follow me on
twitter @bennimack