Task #54571
closed
Epic #55070: Workpackages
Epic #55065: WP: Overall System Performance (Backend and Frontend)
Epic #55656: Optimize overall Extbase performance
Story #54567: Extbase: overall performance of backend modules
Extbase: Avoid TS parsing in BE if not necessary
Added by Felix Oertel almost 11 years ago.
Updated almost 11 years ago.
Description
In backendmodules the TypoScript is parsed on every call. We should give a backend module the chance to avoid loading the TypoScript or see if that is cacheable.
- Tags changed from per to performance
Modules outside of Web> always use the global TS. We should store a parsed copy in the core cache.
Hey Philipp,
thanks for commenting, I see it the same way. I looked through sysext/core/Classes/TypoScript/TemplateService.php and it only caches the TS if TSFE->all is present. I am not finished figuring out, what we can use to identify the cache entry instead of ->all.
Another idea Ernesto mentioned (not sure if it was his idea or if he was just relaying ;) ) was to give every module the option to disable TS parsing alltogether. I don't think that is too good an idea, because we need TS for Dependency Injection and stuff ...
I will try to figure out, how to manage global TS cache in backend in the morning. ;-) untill then, marry christmas to all of you ...
regards, foertel
- Subject changed from Avoid TS parsing if not neccassary to Avoid TS parsing in BE if not neccassary
Because TypoScript caching is part of the core and not extbase, I opened up #54701 over there.
I also adjusted the ConfigurationManagers accordingly, but let's wait, how the caching issue turns out. ;)
- Status changed from Accepted to Closed
this one is dealt with in #54701.
- Project changed from 534 to TYPO3 Core
- Category deleted (
Extbase: Configuration)
- Category set to Extbase
- TYPO3 Version set to 6.2
- Subject changed from Avoid TS parsing in BE if not neccassary to Extbase: Avoid TS parsing in BE if not necessary
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by