[TYPO3-project-4-3] 4.3.0 vs. 4.2.7

[Dan Osipov]

Thanks for this work!!!

The graphs show a patched 4.2.7 - is that 4.2.7 with backported cached 
treelist?

It's interesting that patched 4.3 is slightly higher, but not completely 
equal to 4.2.7

Were the tests done on just one page, or across the site - I remember 
Ingo suggested MySQL cache will kick in with ab requests, making them 
not completely accurate.

Dan Osipov
Calkins Media
http://danosipov.com/blog/

Rupert Germann wrote:
> hi dudes,
> 
> as you might know, I made quite a lot of performance tests the last days
> comparing TYPO3 4.3.0 trunk with 4.2.7.
> 
> These tests showed that the caching performance of TYPO3 4.3 does not (yet)
> reach the performance of TYPO3 4.2.7
> One the other hand 4.2.7 is much slower when delivering processing intensive
> pages with user_int objects or no_cache=1.
> 
> Hmm, how comes? not really logical.
> 
> well, what are the key differences comparing 4.3.0 to 4.2.7?
> caching framework, autoloader and - this made my testresults unlogical - the
> treelist cache.
> In my testcase I use lots of pages with plugins using a pidlist und this
> pidlist is huge (simulated worst case scenario by including the complete
> pagetree).
> OK, that explains the great (+200% and more) results of TYPO3 4.3 when
> delivering uncached pages.
> 
> But there's still the question: why is TYPO3 4.3 slower than 4.2.7 when
> delivering only cached content? 
> one could say that exactly this task should be one of the highlights of a
> caching-framework-driven-cms.
> 
> to get some comparable numbers I did a very bad thing. sorry ...
> ... you'll hate me for this ;-)
> 
> I hacked my current 4.3.0 trunk and re-implemented the old db-only caching.
> The caching framework is completely disabled. I also deleted all caching
> related filereferences in core_autoload.php.
> I placed the content of core_autoload.php as a serialized string directly in
> t3lib_autoloader and I implemented the ux_ class autoloader fix. 
> And last but not least: I changed all get-something-from-a-cache-table
> queries to use ACCESS_TIME instead of time().
> 
> OK, and since I was on it anyway, I backported the cache treelist
> functionality to TYPO3 4.2.7.
> 
> you can find the benchmark results in the linked document:
> 
> http://rgdata.de/fileadmin/user_upload/TYPO3_4.3.0_vs_4.2.7.pdf
> 
> greets
> rupert