Bug #75127
closed
Performance problem compress/concatenate CSS/JS
0%
Description
We've discovered a major performance issue in all version since at least 6.2 up to 7.6 (previous versions might be affected too):
The TypoScript configuration options to concatenate and compress CSS/JS files triple page render time if the page isn't fully cached. For example, render time increases from 350ms to over 1000ms in our installation.
This is the case if at least one frontend plugin on this page is configured that its output shouldn't be cached. It seems that for every request, the files are checked for modifications and maybe the files are re-processed. The only way to ensure that page render times reasonable is to enforce these TypoScript settings (esp. when the bootstrap_package is installed):
config.concatenateCss = 0 config.compressCss = 0 config.concatenateJs = 0 config.compressJs = 0
To fix the issue, compressed/concatenated files should only be created if they aren't available and clearing the cache should remove the compressed/concatenated files.
Updated by Gerrit Code Review over 8 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/47295
Updated by Andreas Kienast about 8 years ago
- Status changed from Under Review to New
Updated by Garvin Hicking 4 months ago
- Status changed from New to Closed
Sorry for taking so long.
Recent TYPO3 versions do have some optimizations in the rendering stack. If performance is a relevant issue, the recommendation would be just like you wrote to disable these options and take separate care of bundling the assets (or using HTTP/2 features, or server-side compression/caching).
I've created a PR on https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-Typoscript/pull/1308 to also mention this in the documentation.
Thus I'm closing the issue here and hope that is fine by you. Let me know if you think this is a mistake, but since it has been like this for many years without getting reported by many people, it is unlikely to receive a dedicated treatment, especially because possible regressions would be likely when cached/uncached frontends and extensions are involved.