[TYPO3-dev] new content object COA_GO - performance - need some advise

[Krystian Szymukowicz]

Marcus 'biesior' Biesioroff wrote:
> 
> Sounds great... works great :) I've got a huge JS dropdown menu, which 
> consumes about 80% (ca. 800ms) of time needed for page generating ... 
> every page :/. 

So this is a really big menu. And a really good case to use COA_GO :)


> There is some problem with first method mentioned by you - 
> beforeCache_db - when using with TemplaVoila the COA_GO content doesn't 
> show on the page where it was generated (but on the other pages it is 
> OK). Second and third ways works (probably) as they should do... :)

Whups - it was a simple bug and has nothing to do with TV. I've focused 
on testing afterCache_file and ajax_file and did not test properly the 
first method beforeCache_db. Sorry.

I've uploaded new version [1] - it would be great if you can test it. Tnx.
[1] http://prolabium.com/coa_go/coa_go.zip


> I have a large implementation, on the almost-production state, so I will 
> test more elements (as you mentioned few LATEST and LIST views) to check 
> how does it work in general use... :)


Nice to hear that COA_GO has just found its way in first production 
site! As I can see in your case it was a big time generation improvment.

I am sure that integrating tt_news LATEST as "cache.type = ajax_file" or 
as "cache.type = afterCache_file" will make general performance of your 
site really great as there will be no need to clear cache of pages that 
have tt_news LATEST.

If you have any trouble do not hestitate to ask.


--
grtz
Krystian Szymukowicz