Bug #55023
List Module in Backend is very slow due to Extbase's Typoscript parsing
Status: | Closed | Start date: | 2014-01-15 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | - | Spent time: | - | |
Target version: | 6.2.0 | |||
TYPO3 Version: | 6.2 | Is Regression: | Yes | |
PHP Version: | 5.4 | Sprint Focus: | ||
Complexity: |
Description
While profiling the Backend with XHProf I found that each click on the list module triggers a complete TypoScript parsing.
This is done in sysext\extbase\Classes\Configuration\BackendConfigurationManager.php->getTypoScriptSetup()
this method actually has an internal cache for typoscript but this cache only hits when getTypoScriptSetup() is called 2 or more times during the same request. If I hit the list module with the same pageID again a new request is triggered and the complete TypoScript is parsed again.
Making this cache persistent (e.g. by putting it in the Caching Framework) would be a great speed improvement for the Backend.
Related issues
History
#1 Updated by Markus Klein over 1 year ago
I'm not sure, but I guess there's a ticket somewhere for this.
#2 Updated by Rupert Germann over 1 year ago
- File callgraph_recordlist.png added
I attached a callgraph which shows one request on the list module.
As you can see most time is wated in the core classloader and the extbase classloader.
#3 Updated by Rupert Germann over 1 year ago
- Status changed from New to Closed