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

[Krystian Szymukowicz]

hi

I'd like you to show a way to decrease page time rendering in TYPO3.

The example would be SINGLE + LATEST at the same page.

HOW IT WORKS NOW?

Right now TYPO3 will generate LATEST at each first hit of a page.
Click on news A and TYPO3 render LATEST
Click on news B and TYPO3 render LATEST
Click on news C and TYPO3 render LATEST
...again, and again....

If you have 1000 news then LATEST is generated 1000 times.
This is bad, is not it?




HOW IT CAN BE IMPROVED?

The solution is simple. TYPO3 needs to generate LATEST once, cache it 
and then should use it whenever it is needed.

How can it be done?

Its very simple:
1. Install extension COA_GO 
http://typo3.org/extensions/repository/view/coago/current/

2. Change you typoscript LATEST code with 3 chars. This is no joke. Its 
enough to add 3 chars really :)

EXAMPLE.

This was your LATEST typoscript:

temp.myLatest = COA
temp.myLatest.10 < plugin.tt_news
temp.myLatest.10 {
code >
code = LATEST
...
}


AFTER change:

temp.myLatest = COA_GO
temp.myLatest.10 < plugin.tt_news
temp.myLatest.10 {
code >
code = LATEST
...
}


DONE.



5 minuts of changes, 3 chars added and it can lower the page rendering 
time about 100-200ms depending mainly on:
a) how many news in LATEST,
b) if you use realurl (the link generation is longer then),
c) how fast is your server.


Give it a try! It is simple.


BTW: COA_GO can also put together nc_staticfilecache with *_INT cached 
objects. Its done by fetching static LATEST using AJAX. Imagine you do 
not have to clear the nc_staticfilecache cache each time you add news. 
Now with COA_GO you set cache.period to 10 minutes and LATEST is 
regenerated automatically.


And of course you can use it not only for tt_news LATEST but for each 
content object that in the same form can be repeated at many pages. 
(this is why LATEST is the best example :)

--
grtz
Krystian Szymukowicz