Why is Revoloution so slow?

Quote from: peelay at May 28, 2012, 04:48 PM

Hi There,

I'm looking for some help with improving performance as well. I'm working on a site that's currently ready to go live but the client doesn't want to launch with the slow performance. The backend they can live with the speed, but the 3-6 second load times for simple front end pages just isn't acceptable.

There can be HUGE differences betwenn hostings. this is sometimes even true if you are measuring performance for several accounts hosted at the same provider.

I'm working on a MODx Benchmark. Until it is finished, you can use the attached files instead:

* download both files
* remove the .txt entension,
* modify db information inside dbtest.php
* and upload both files to a hard to guess directory on your server (for example dsfsdfsdfsdf).

Let them run several times.

* http://www.example.com/dsfsdfsdfsdf/dbtest.php
* http://www.example.com/dsfsdfsdfsdf/php-benchmark.php

Post the results in a new thread or send me a pm. I have a couple of results to match against. If your hosting environment is to blame for your bad performance this should give a hint.

If you are having problems with the execution of snippets or chunks, you should be using the executioner snippet by opengeek to pin down the culprit.

I have a modified version in my gist repository: https://gist.github.com/1903200. you can find the original code here: https://gist.github.com/606684

If you have questions how to use it, send me a pm.

Regards,

pepebe [ed. note: pepebe last edited this post 11 years, 11 months ago.]

Ok, this is off-topic.

@Admin or FWIMC

PLEASE change the template for the toolbox on the right side (the one with remove, modify, quote, etc).

* "remove" should not be the first entry.
* it should have some whitespace around it (like for example "report to moderator")
* and most of all it should ask you for confirmation before it erases you post.

I'm not sure about the last thing, but I remember it didn't do that in the past.

Regards,

pepebe

[ed. note: pepebe last edited this post 11 years, 11 months ago.]

Hello,

Another one here.

I have just started to use MODX 2.2.2-pl (traditional).
It is running on my MacbookPro(OSX Snow Leopard), 4Gb mem, MAMP-Server (apache 2.0, PHP 5.2.10, mysql 5.1.37).

Working in the Manager is very very slow. It takes sometimes up to 30 seconds to switch a screen. This is in all browsers, Chrome, Safari, Firefox. When working in MODX-Manager I see the httpd processes taking a lot of CPU.

System Settings:
- "compress_css" and "compress_js" are enabled
- manager_html5_cache is enabled
- All caching options are enabled

I cannot imagine we, in this thread, are the only ones experiencing this. Are there any people out there who are running a blazing fast manager in Revo 2.2.2-pl manager?

Thanks,

Bert

I load manager views from 2.2 in under a second (about 950ms per view) on my MacBook Pro (OSX Lion), 8Gb RAM, nginx 1.2.0, PHP 5.3.13, mysql 5.5.20). And I don't see any CPU issues in top anywhere in the stack when loading them. This is about the same as I had previously when using Snow Leopard with apache 2.2, PHP 5.3.9, and mysql 5.1.

I'm not sure if MAMP includes it, but if you don't have APC installed/enabled, I highly recommend it. Caching PHP classes/files in an opcode cache can make a big difference in performance.

MODX 2.2.0-pl2
2009 MacBook Pro, 8Gb RAM

MAMP:
Apache/2.2.17 PHP/5.3.6
MySQL client version: 5.5.9
APC enabled

Average Manager load time 1.5 - 2.5 seconds, depending on whether resource tree is fully collapsed/expanded.

I've recently been working on the same MODX version installed on a shared hosting account on the other side of the world (Australia -> Germany) and it has never been slow to the point of frustration.

@bert - can you go into Chrome Dev Tools, Timeline tab, uncheck the purple 'rendering' box and post a screenshot of your 30 second page load? Alternatively have a look through and see which requests are taking so long...

Hello Opengeek, Lucas,
Thanks for the help and replies.
The following is what I did:

1) Enable APC in MAMP.
This gave me some improvement, but not much.
(Of course did a couple of requests first to let the APC cache fill itself)
2) Run the TImeline in Chrome DevTools.
The action I did was switching from one Resource to another.

The timeline.json file is zipped and attached. (213Kb). And also some screenshots of various requess.

Since other CMS's are very fast (Magento, Joomla) on the same machine, I expect this is something in my MODX Revo installation. Also MODX-Evo is fast.

Small extra remark: I just did some support on a Revo 2.0.8-pl site and noticed that also that one is fine to work with, so no performance problems in Revo 2.0.8-pl.

Looks like the problem is introduced in 2.2.2-pl.

Ok, I have moved the whole website to a testserver of more serious nature. And now it works fine.

So, must have been my MAMP installation in combination with MODX-Revo-2.2.2pl.

Thanks to the people who took the trouble of investigating.

(Funny that you can see how many people downloaded the attachment)

Hi Bert - I haven't received an email notification so hadn't realised you'd posted back. Glad you seem to have it sorted though.

What's different about the new server compared to your MAMP install? It might help out some others who are also having performance issues.

I was having a similar problem with XAMPP, which used to be extremely fast for me with Revolution. I was getting 5- to 10-second page loads in the Manager and in the front end, even with all virus checking turned off. It seems like the newer versions of MODX don't play well with some localhost installs.

Upgrading XAMPP helped quite a bit (though it was a major pain), but it's still faster for me to work on a remote site than to work locally.



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