Task #54571: Extbase: Avoid TS parsing in BE if not necessary - Core - TYPO3 Forge

Core Indexed Search Linkvalidator Release Cycles Team Resources Workspaces & Versioning TYPO3 CMS Usability Team Community Extensions Distributions Feature-Requests TYPO3 6.2 Projects (+)(Archived Projects)

Task #54571

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 over 1 year ago. Updated over 1 year ago.

Status:

Closed

Start date:

2013-12-22

Priority:

Must have

Due date:

Assigned To:

Felix Oertel

% Done:

Category:

Extbase

Spent time:

Target version:

6.2.0

TYPO3 Version:

6.2

Complexity:

PHP Version:

Sprint Focus:

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.

Related issues

History

#1 Updated by Felix Oertel over 1 year ago

Tags changed from per to performance

#2 Updated by Philipp Gampe over 1 year ago

Modules outside of Web> always use the global TS. We should store a parsed copy in the core cache.

#3 Updated by Felix Oertel over 1 year ago

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