[Typo3-dev] High parsetime for *_INT objects

[Peter Niederlag]

Hi,

Simon Ihmig schrieb:
> Hi there,
> 
> I realized some strange behaviour regarding the parse parse times I am
> unable to explain:
> I have a site with 100% fully cached pages (i.e. no USER_INT or COA_INT
> objects). The total parsetime as shown in the Admin Panel is around 17ms.
> 
> But when I change one COA object into a COA_INT (it does nothing more than
> printing the current date/time), the parsetime changes dramatically:
> I have a new entry "/Parse template" in my Admin Panel TypoScript output
> with around 50-60ms and total parse time is 80-90ms.
> The noncached objects execute in virtually no time (0ms).
> 
> What's the reason? It should not be that just because of the fact that I
> have a non-cached object somewhere in my TS tree, the parse time increases
> by 400% (an thus server load!). While 90ms parse time doesn't sound very
> huge, IMHO it can have a huge impact on high-volume sites (compared to
> 17ms).
> 
> Any ideas?

on real quick glance I am not so much surprised.

a) no user_int => take page from cache and deliver
b) just one smal user_int => take page from cache and search/replace 
tokens for user_int then deliver. I guess there is some ressources spent 
going through all those TYPO3-API-calls needed to include that user_int.

You could do some further investigations where the parsetime is spent if 
you need more information.

how is parsetime if caching is disabled at all?

Cheers,
Peter
-- 
Peter Niederlag
http://www.niekom.de * TYPO3 & EDV Dienstleistungen *
http://www.typo3partner.net * professional services network *