[TYPO3-ttnews] a tip - how to improve performance of SINGLE + LATEST at the same page

Krystian Szymukowicz t33k.RE.MO.VE at RE.MO.VE.prolabium.com
Tue May 5 13:47:48 CEST 2009


Patrick Gaumond wrote:
> Krystian Szymukowicz wrote:
> 
>> So far you are the second person I know, which tested this extension 
>> and was really satisfied with time rendering improvements.
>>
>> I hope there will be more people that will test it and find it useful.
> 
> May I suggest you promote your work in the group: typo3.performance ?
> Refresh your newsreader groups if you don't see it. In theory people 
> there should be delighted by such work...

Thanks for that hint Patrick! I will send info there as soon as I 
prepare some better documentation and real case studies.

> OT: Is there any downside to COA_GO ? Any reason why it shouldn't go 
> into Core ?

Downside of COA_GO?

The default caching of COA_GO (beforeCache_db) has no downside at all. 		
Simple but quite powerful and this for sure can go to core. Even the 
cache period in this case is not needed.


The two remaining methods of caching that COA_GO offers are:
a) including cached content from files after the page is taken from 
cache (afterCache_file)
b) including the cached content from files using AJAX (afterCache_file_ajax)

Both support cachePeriod, they are tested and works well but the way of 
regeneration after the cachePeriod expires is not perfect yet. It simply 
calls page with no_cache parameter - not so bad but could be better. 
I'll have to work on this. Any hints how to make it better appreciated.


--
grtz
Krystian Szymukowicz


More information about the TYPO3-project-tt-news mailing list