Improved Performance and Stability
The base logic for handling installed extensions and composer packages was backported originally from TYPO3 Flow and used since version 6.2, however most of the logic was never used in the TYPO3 CMS environment. This area was fully cleaned up and slimmed down, requiring less complicated code and less server memory in every Frontend and Backend request, but also act as a more robust solution than ever before.
Composer Class Loader
Loading PHP classes from the filesystem was originally done by a custom functionality introduced in TYPO3 6.2. Earlier this year, the standard functionality from Composer
was integrated, but the TYPO3 functionality still acted as fallback for installations not set up through the command line with composer. This has now been streamlined and the “old” class loading functionality was migrated and unified to be using composer, which is only triggered on installation of an extension and is cached separately.
Templating Engine Fluid
Lots of standard view helpers of the rendering engine Fluid were changed to improve performance. This has a positive effect in the backend and leads to significant performance improvements in Extbase extensions. This is a gift to users of the system and developers at the same time since all changes are fully transparent and need no code change in extensions that use Fluid - rendering is just quicker out of the box. In general, working inside the TYPO3 backend feels faster.