Optimising / caching TV values

Quote from: ncrossland at Apr 21, 2011, 07:34 AM

On the other questions - is there any room for optimising TV retrieval in 2.2?

On the site I’ve been testing on (which has quite a few resources with around 12 TVs) getResources was taking >7 seconds to run. With my optimisations its down to <4 seconds, but the ultimate delay is the calls to renderOutput

TV’s were optimized for MODX 2.1, but in order to do what TV’s do for presentation, they have to be able to calculate dynamic values per TV — if you don’t need the processed TV values, it will be much faster. And not using TV values at all is optimal with getResources. Regardless, cache the data properly and you will avoid the overhead on most requests.

This idea of including specific TVs is absolutely the best approach here.

I have a list page and detail page.
The detailpage has about 25 tv's, the list page only shows 3.

The loading of the list page takes about 15 seconds.

So if i'm correct it is possible to only load the tv's i would like to show on my list page to reduce the loadtime?

#####

solution:

[ed. note: fourroses666 last edited this post 12 years, 2 months ago.]