Wir machen es kurz und knapp: Es ist wieder einmal soweit – ein neuer TYPO3 Benchmark steht an. Vor einigen Tagen wurde die TYPO3 Version 6.2 beta1 released – wir wollen natürlich direkt wissen, wie diese aktuell im Performance-Vergleich zur 4.5 LTS steht.
Laut einer aktuellen News zu TYPO3 6.2 werden Arbeiten an der Performance in der nächsten Zeit durchgeführt. Hier heißt es:
Speed Speed Speed
During the last code sprint before feature freeze and still being debated in the team is the need to regain performance in TYPO3. We are aware that since 4.5 a lot of refactoring made the code cleaner and more robust, but in certain scenarios the performance got worse from release to release. Due to the fact that releases between the LTS releases (4.6, 4.7, 6.0, 6.1) were not used so much by major installations, this performance degradation hasn’t come to the attention, and most will be hit by it first time when upgrading from 4.5 to 6.2.
To minimize the impact the CMS team is currently working hard (i.e. in #52949) to identify and potentially solve the most important performance issues.
Benchmarking is a difficult topic, and we currently have no standardized way of benchmarking TYPO3 Core to identify exact commits which affected the performance. The difficulty lies in setting up correct installations and creating useful scenarios which can provide useful information at the end. The art lies in being able to interprete the statistics generated by benchmarking tools and it’s impact.
The idea of hosting a „Performance Code Sprint“ popped up. It could be something to be planned for November.
But in general we invite every performance interested TYPO3 developer or integrator to help us with profiling, identifying bottlenecks, and working on solutions – instead of simply complaining about it. Let’s look into the future and not in the past.
Nun beginnen wir aber mit unserem Test.