[TYPO3-english] huge Realurl and cache db tables!!!

Dmitry Dulepov dmitry at typo3.org
Fri Feb 6 12:21:48 CET 2009


Dmitry Martynenko wrote:
> But I noticed that tx_realurl_urlencodecache table has field internalExtras.
> It used to store optional information about FE or BE user and for url_hash calculation.
> But it leads to (records * 2) again and only store value, never reading it!
> Generates URLs are the same: (id=flats&unid=91086) == (sale/flats/object/91086/).
> For example:
> url_hash  origparams  content  page_id  tstamp  internalExtras
> 2bc33f02b040385732f140310366d2c2 id=flats&unid=91086 sale/flats/object/91086/ 76 1233838407
> e619ee389d4f442c7871db9eaf06c877 id=flats&unid=91086 sale/flats/object/91086/ 76 1233661167 a:1:{s:7:"feLogin";i:1;}
> May be it is kind of "unused" feature?
> And avoiding of it can improve RealURL and TYPO3 performance?

There are some historical artifacts, yes. I slow get rid of them. For example, next version of RealURL will have optimized path cache.

For the decode cache I cannot tell anything right now. Please, write a detailed bug report about it. I will check and get rid of all unused fields. I plan to optimize RealURL to the maximum.

Dmitry Dulepov
TYPO3 core team
"Sometimes they go bad. No one knows why" (Cameron, TSCC, "Dungeons&Dragons")

More information about the TYPO3-english mailing list