[TYPO3-core] RFC #9657: Instantiate time tracker as null object if not really required

[Rupert Germann]

FYI: committed attached v3 patch to trunk rev 5881

only change compared to v2:
I removed function debug_typo3PrintError() from the null class because 
it is never called.

I also tested succesfully that it still works with the new message which 
was introduced by 11599 ( TYPO3 dies without an error ....)

greets
rupert



Rupert Germann schrieb:
> Hi,
> 
> this is a SVN patch request.
> 
> Type: performance improvement
> 
> Bugtracker references:
> http://bugs.typo3.org/view.php?id=9657
> 
> Branches: Trunk
> 
> Problem:
> In the TYPO3 front-end an instance of t3lib_timeTrack is created in the 
> variable $TT. During the front-end rendering process the time required 
> to parse and execute several scripts and modules is stored using this 
> object. When there's no be_user logged in this information is never used 
> and so timetracking only eats up precious performance.
> 
> Solution:
> Use a null object with empty methods in general and only use the current 
> time tracker if a logged in be_user views pages in the front-end.
> 
> 
> benchmark results:
> 
> cached pages:
> trunk:        293.83 trans/sec    100%
> patched:    308.95 trans/sec    105%
> 
> uncached pages:
> trunk        34.47 trans/sec        100 %
> patched     37.03 trans/sec        107 %
> 
> 
> greets
> rupert
> 
> "There shall be no new TYPO3 version delivering content slower than its 
> predecessor!"
> 
>