[TYPO3-v4] Core performance for 4.6 and beyond

Tolleiv.Nietsch info at tolleiv.de
Tue Feb 8 12:48:20 CET 2011


Hi,

> ** We could concatentate important (read: always needed) classes in one
> file to reduce filesystem lookup overhead. Making makeInstance aware of
> that shouldn't be too difficult (not tried yet). This will *add*
> performance if we refactor important classes to smaller things from
> which not everything is needed for full cached access.

isn't APC/eAccelerator/Zend* supposed to help with that in a much more 
efficient way? I'd prefer not to do something like this.

The other points sound reasonable. But before we refactor something, 
there should be some kind of regular public performance monitoring so 
that we've some way to compare results. Maybe at least a benchmark 
script could help to check wether supposed changes help to improve 
things or not.

Btw. whenever I read "significant refactoring" related to v4 I get a bit 
desperate because isn't that what we called v5 ;) / I've the same 
feeling related to your bootstrapping post - right approach but is it 
worth to do all this in v4?

Cheers,
Tolleiv



-- 
Tolleiv Nietsch
www.tolleiv.de - www.aoemedia.de
Twitter: http://www.twitter.com/tolleiv


More information about the TYPO3-project-v4 mailing list