Performance Tuning

Hi;

I’m getting complaints from a couple clients that the manager interface is too slow, [in my opinion it’s just fine] I was wondering if there are any performance tuing tips floating around? maybe I can goose a bit extra speed out of this thing.....

- on a MediaTemple DV4.0 4GB/Ram - so no hardware issues at all
- I have enabled gzip compression on all appropriate file types in the webserver config.
- I’ve tweaked the modx cache settings as much as I can see possible
- removed any extra/useless packages
- updated to the latest release

Any other steps that can speed up the manager?

-thanks
-sean

Don’t use IE.

I gave up on IE years ago - still have to use it for client testing though

in fact, I find chrome to be the best behaved with modx manager & has what appears to be the fastest js engine, I tell all my clients to use it for modx & I know for sure that this particular client is using chrome....

ie does suck, but in this case it’s not the culprit.

-sean

You can disable the news feeds (go to System -> System Settings and put "feed" in the search box). That will speed up the initial load.

I can try that, but it’s mostly working with articles.....

The site is relatively large, around 300 articles/pages.... could that be affecting things?

How about disabling the refresh on the resource tree, I’ve seen hints that this might be done, but nothing solid.

-sean

Quote from: sean69 at Mar 15, 2011, 08:37 AM

I can try that, but it’s mostly working with articles.....

The site is relatively large, around 300 articles/pages.... could that be affecting things?

How about disabling the refresh on the resource tree, I’ve seen hints that this might be done, but nothing solid.

300 is tiny. We have Revolution sites being supported with 10’s of thousands of Resources.

Do you have concat_js and compress_js enabled? compress_css, too? You can find it in system settings "backend manager"

Hi - Yes, I do have the compression setup in modx, additionally I am using mod_deflate to deliver.....

now looking at caching & headers, found something odd. I’m using mod_expires - it works fine for what seems like every site on the server, but curiously enough not the modx sites [nor the magento sites]

Is there something in modx that is rewriting headers somehow?
here’s what I get:

Date: Tue, 15 Mar 2011 15:08:40 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.5
Set-Cookie: PHPSESSID=xxxxxxxxxxxxxxxxxxxxxxxx; expires=Tue, 22 Mar 2011 15:08:40 GMT; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 20
Keep-Alive: timeout=5, max=500
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8

here’s what I have in an .htaccess:
ExpiresActive On
ExpiresDefault "access plus 10 years"

-thoughts?
-sean

MODX uses PHP sessions and the PHP configuration for session.cache_limiter controls how the headers are written.