[TYPO3-core] RFC #17693 performace of cachingframework: alternative dbbackend

[Bjoern Pedersen]

Am 24.02.2011 19:47, schrieb Peter Russ:
> 
> Frankly speaking I don't get the benefit of code dublication as this
> pretty similar to dbbackend.
> 
> 1) Ever tried to fix slow result by just improving the index?

Yes, but mysql does not use any index, if there are column calculations
in the query.

> 2) There is STILL the drawback, that the API always query the ->has
> before the ->get: 1query to the db is needless as the first could
> already receive the result and store it in global ;-)

No, has() is never called for the dbbackend before get.

> 3) Why should I use a very high number to indicate that something should
> last forever instead of 0 ?  Ever checked db directly and tried to
> remember "forever"?

Well, 'forever' is anyway a broken concept for a cache.

> 4) From point of service/support it would be a nightmare to change the
> layout for the db design.

The same would then be true for different backends.

> -1 for this patch and ALL versions!
> 
> Peter

Björn