[TYPO3-dev] typolink generation high parsetime

Popy popy.dev at gmail.com
Fri Oct 26 11:35:31 CEST 2007


2007/10/26, Steffen Kamper <steffen at sk-typo3.de>:
>
> do you thought about using MySQL Query-Cache? This was also discussed by
> core and does exactly the same.
>
I don't think it's the best solution : as Bartosz said, queries are sent to
mysql.


2007/10/26, Mads Brunn <mads at typoconsult.dk>:
>
> Can't use Mysql query cache for this since starttime and endtime is
> queried with different values on each hit.
>
In this case this is not a problem, as all queries performed on a page hit
have same starttime & endtime check.

2007/10/26, Elmar Hinz <elmar07 at googlemail.com>:

> Hi,
>
> What is required? A list of the Id's of linkable pages. How big is such an
> integer? A few bytes. Let's calculate.
>
> Having a large page with 10.000 of accessible pages that what result in a
> dimension of 100 MB. Having only 100 Pages the dimension would be 1 MB.
>
> Is it high or low?
>
> What is the basical memory footprint of a T3 page without links?
>
> Regards
>
> Elmar
>
I'm sure you'll agree to say that topy3 already needs too many MBs to
work...
By the way, you have to make a big SQL query to get all your "accessible"
pages, php will need a few time to access to a value in a long array... and
I really don't like to ask to mysql to give me something that I'm not sure
I'll use it...

Yes, I know, I am a bit crazy ^^

-- 
Popy

Vulnerant omnes, ultima necat.

http://popy.sytes.net




More information about the TYPO3-dev mailing list