Revolution 2.2.2 Performance improvement is REAL

A page on 2.2.1 took 22 seconds to load (uncached) and on 2.2.2 it's down to <7 seconds.

This is a great improvement so thank you for this. Prior to this I was getting the user to batch all edits and then getting them to load all pages to rebuild the cache. The 22 second page only takes 0.6 seconds to load when cached.

With such a dramatic improvement in performance I think it's ok to let the user make adhoc edits to the site.

Whoever it was I'm pleased they noticed the handbrake had been left on in 2.2.1 and below.

That's still 6 seconds too slow uncached...

Is this a Resource with multiple getResources calls that do some filtering or sorting by Template Variables perhaps?

Yes

2 x getResources with TV's and 6 x Wayfinders

Are the Wayfinder and/or getResources calls cached?

[[Wayfinder ... ]]

That can speed thing up a lot if you can clear the cache manually when things change.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Are we talking at cross purposes here?

All snippets are cached. On 2.2.1 and 2.2.2 after the page has been visited and the cache built it only take 0.6 (nought point six) seconds to load. This is great and I'm happy with this.

When the cache got cleared the first time page load (no cache yet) has fallen from 22 seconds on 2.2.1 to <7 seconds on 2.2.2. I'm delighted with this and the purpose of my post was to highlight the performance improvement in 2.2.2 is real and genuine and I'm grateful for it. I'm now upgrading all my sites.

Hi Mark,

I guess your speed-problem is wayfinder. We have the same problem. We have a big site containing ~1.500 pages and the wayfinder-snippet needs uncached more than 3 seconds. Cached it is great, but uncached it is really really bad.

Unfortunately there is no way in MODx to make small changes on a webpage for example adding a word in a sentence without clearing the whole MODx-cache on saving a resource. There is no way for example to keep the wayfinder-result in the cache on saving.

Therefore at the moment we cannot let our editors use MODx. Instead of this we collect all their correction-wishes and implement these corrections once a day an afterwards put all important pages by our own script again in the cache. You can imagine what the editors think of us ...

That is really a big problem for our work which makes it not possible for us to use MODx as a normal CMS ...

Letti

Quote from: sparkyhd at May 05, 2012, 03:39 AM

Are we talking at cross purposes here?

I was simply curious about your remaining uncached bottlenecks. I think it's time to take a serious look at re-engineering Wayfinder for better performance if it is really taking that long. I don't have any Wayfinder calls on my sites that take more than half a second, so this is why I am curious as to what is going on with your Resources...

I don't have any Wayfinder calls on my sites that take more than half a second,

Can you just tell us how many resources do you have all together? And how many menu-levels?

We have 3 levels and ~1.500 resources leading to this slowness of wayfinder uncached ...