MODx Revolution Extremely Slow

Our installations of revo are also slow! (tested on multiple servers) When the cache file is created it will be okay, but before that the sites are very slow!

We uses mostly normal resources to create our sites (like news pages, blogs, agenda etc. etc.) and uses getResources. Also a common use is the ’If’ and ’ifEval’ snippets for some dependencies inside the pages. Our loadtime is about 20 seconds. I noticed a ’sleep’ in the database when requesting a page, this ’sleep’ is gone when the page is showing up. Does anyone have ideas?

On one of my sites I get

Not Cached: size: 18.1kb Load 2.41s
Cached: size: 18.1kb Load 538ms

I have at least
- 3 menu wayfinder calls
- 1 getResources
- each getResources item has a submenu so add another 4 Wayfinder calls

One another page

Not cached: size 25.3kb load: 3.23s
Cached: size 25.3kb load: 593ms


I have at least
- 3 menu wayfinder calls
- 1 getResources
- each getResources item has a submenu so add another 10 Wayfinder calls

So I can definitely see a decrease in performance when I have more things happening in the page
Results taken from firebug with firefox

Quote from: bertoost at Feb 16, 2011, 08:15 AM

Our installations of revo are also slow! (tested on multiple servers) When the cache file is created it will be okay, but before that the sites are very slow!

Exactly the same. Not to mention, when it comes to several thousand resources (2000-3000). Recaching sometimes takes too much time(30-40s and more) on VPS. I try lots of server-php-mysql combinations (php 5.2x, php 5.3x, with and w/o APC, diffrent MySql versions) on VPS, on localhost Windows and Debian... I try with disable caching, but it was even slower.

Quote from: dj13 at Feb 16, 2011, 07:58 AM

This is a general problem.

-1
There is a _general_ problem that only a handful will give constructive criticism and
help out improve this open source product.

There is a _general_ problem that people who now rant and having bad experiences with Revo ditched EVO thinking they had too!
Evolution will be supported and maintained for the foreseeable future as it is an ideal platform for many types of sites and is deployed on hundreds of thousands of sites worldwide.
http://modxcms.com/forums/index.php/topic,61620.msg350082.html#msg350082

There is a _general_ problem that developers are selling websites and functionality built on Revo (or any system)
they haven’t first figured out themselves.

Try MODX EVO
http://sottwell.com/manager/
Username ’guest’, password ’guestuser’.

Try MODX REVO
http://www.trymodx.com/

XAMPP your local webserver
http://www.apachefriends.org/en/xampp.html

Quote from: mrhaw at Feb 16, 2011, 10:20 AM

There is a _general_ problem that people who now rant and having bad experiences with Revo ditched EVO thinking they had too!
Evolution will be supported and maintained for the foreseeable future as it is an ideal platform for many types of sites and is deployed on hundreds of thousands of sites worldwide.

I agree, if you *really* don’t like Revo use Evo.

Although with Revo deemed "the future of MODX" according to the front page of the site, you can understand why some people will jump ship in the hope of something better or at fear of being left behind.

It’s worth it to note, however, that in our experience, 98% of "slowness" with Revo ends up to do with the following:

* Poor or misconfigured hosting environments (often the case)
* Using IE7 or earlier
* Bad caching strategies being employed on the site, such as too much ! uncached or using too many filters/eval/if statements when Snippets should be used
* Using Ditto instead of getResources
* Trying to run a modern JS app on an ancient computer

Again, if you want a simple, pared-down product that works in older, deprecated systems and environments, try Evolution. For those wanting a product that is where the future of the web is heading, Revolution is and will be your product.

Again, if you want a simple, pared-down product that works in older, deprecated systems and environments, try Evolution. For those wanting a product that is where the future of the web is heading, Revolution is and will be your product.

No wonder I prefer to stay with Evo! That sounds like my knees! (and you owe me a keyboard cleaning for making me laugh with a mouth full of Chocolate Truffle tea!)

I’m with Susan.
We seem to be getting very mixed messages about the status of Evolution, additionally I think there’s a danger of marginalising current Evolution users with statements like..

For those wanting a product that is where the future of the web is heading, Revolution is and will be your product.

Surely there are many of us happy to continue developing small to medium sites with reasonably sophisticated functionality that we can readily hand over to clients for editing using Evolution.
I’m certain pretty much any of it could be done with Revo, but that, in itself is no reason to change.
There seems to be a general ’tone’, for want of a better word, developing, questioning the use of Evolution instead of Revolution.
Shouldn’t we see them as two distinct, but equally valid, products offering different solutions to meet varying needs.
I freely admit that I’m comfortable with Evo and have a certain reluctance to invest the time getting up to speed on Revo, perhaps I’m just too old and set in my ways.
Oh well, at least I got it off my chest.
Long live Evolution

So far, as I follow the forums, I’m seeing far too many problems with Revo stemming from its relative complexity. Nobody but the dev team seems to fully grasp the user management system, for example. Lots of odd problems with various server configurations. The javascript appears to be fragile and a bit flaky. Lots of plain old installation failures for myriad and unknown reasons. In my opinion, if you want a sure, stable product that Just Works, Evo is your product. So far, except for contexts (and these are the source of lots of questions and problems as well) I haven’t seen or heard of anything Revo does (perhaps more quickly and natively) that can’t be done just as well with Evo. Revo is like ultra-modern art; I can appreciate the technique and all, but that doesn’t mean I want in on my walls.

Because of the book, I was forced to get up to speed with Revo. Now that I am, I find it quite frustrating to work in Evo. I miss quick update and xPDO and I mutter to myself every time I have to do the Resources ->Manage Resources->Select tab->Select element thing when I could just click on the element in Revo (or better yet, do quick update without losing my place).

It also makes me extremely grouchy not to be able to clear the cache in a popup without having to go through the whole sequence of selecting the element I was working on again.

I can’t wait until I have time to convert Bob’s Guides to Revo.

Maybe it’s just me.