[TYPO3-core] RFC: #0011505: TYPO3 4.3 is slower than 4.2.8 -> re-implement native db caching

Oliver Hader oliver at typo3.org
Tue Sep 15 19:02:45 CEST 2009


Hi Dmitry,

Dmitry Dulepov schrieb:
> Hi!
> 
> Mathias Schreiber [wmdb >] wrote:
>> Take the classic library example.
>> You want a book - but there is not one clerk helping you out, there are 20.
>> And every clerk needs to be tapped on the shoulder "hey, need you".
> 
> I think it may also be tag handling. We old system it is very simple: you have a pid and that's it: select or delete by the integer pid. With the new system there are string tags (like 'pages_345'). Strings are already slower, they are not indexed well in databases. Also they are so generic that they will never be as effective as old good pid. Caching framework is bound to be slower than the old method. Generic solution is almost always slower than the specialized one.

For the case "read a completely cached page from the cache" no tags are
used - just the identifier is used in thtat case. However, tags are
currently stored in a list - selecting for one tags means using LIKE
queries and thus a full table scan.

There's a patch for it in the bugtracker:
http://bugs.typo3.org/view.php?id=11903

olly
-- 
Oliver Hader
TYPO3 Release Manager 4.3


More information about the TYPO3-team-core mailing list