[TYPO3-dev] performace of cachingframework

Bjoern Pedersen bjoern.pedersen at frm2.tum.de
Fri Feb 18 17:15:20 CET 2011


Am 18.02.2011 11:51, schrieb Peter Russ:
> --- Original Nachricht ---
> 
> This assumption is correct on your machine. But on high load sites where
>  values are cached for some secs or mins it looks totally different:
> There could be several 100s or 1000s of records with the same key before
> GB....
> 
> It would help a lot if developers would realize that TYPO3 claims to be
> an "Enterpise CMS" and this more than just "runs fine on my machine" ;-)
> 
> Peter.
> 
> 
Yes, that is valid point.

A few more infos that I need from the cache specialists:
is the has-function actually used anywhere except in some BE's
internally? A grep on the core sources did not find anything. There were
just hits in the tests and in swiftmailer (implementing it's own cache)
and in extbase, also not using the normal cache.


If it is not really used, i would suggest to deprecate it to avoid a
usage pattern like:
 if(cache->has(id)) then cache->get(id).

Björn




More information about the TYPO3-dev mailing list