Benchmark: ModX is slow!

We have modx powering a high traffic adult site - visitors to the site, view a substantial volume of high res images, access hundreds of content pages, and use several dozen types of contact forms. The site takes 90,000 hits a day, it’s hosted on a shared server plan over at hostgator. It eats on average, 19gb in bandwidth each month.

Ah! Thanks a lot. That’s really good news =)

May I ask what site you’re running? Not for fun, but for ecucational purpose. I just want to find out how quickly it responds.

Do you have any more tip about disabling plugins, or what plugins/API-functions not to use if you want speed over functions?
I know that i.e disabling "resolve ip" speeds up the site a lot, but I’m curious about more tweeks, easy "click & disable" and more "disable in source"-kind of hack =)

Thanks

Quote from: Stabilovic at Feb 27, 2007, 04:03 AM

We have modx powering a high traffic adult site - visitors to the site, view a substantial volume of high res images, access hundreds of content pages, and use several dozen types of contact forms. The site takes 90,000 hits a day, it’s hosted on a shared server plan over at hostgator. It eats on average, 19gb in bandwidth each month.

Ah! Thanks a lot. That’s really good news =)

May I ask what site you’re running? Not for fun, but for ecucational purpose. I just want to find out how quickly it responds.

Do you have any more tip about disabling plugins, or what plugins/API-functions not to use if you want speed over functions?
I know that i.e disabling "resolve ip" speeds up the site a lot, but I’m curious about more tweeks, easy "click & disable" and more "disable in source"-kind of hack =)

Thanks

Hi, sure - PM for the URL, it’s a adult content site - nothing "x-rated", still, people here apparently take offence to modX being used for such purposes.

Turn the counters off :-

administration -> system configuration

Turn-off "log visits" & "resolve hostnames"

Your hosts will be very happy once you have, we use analytics so they’re unnecessary overheads - actually, they cooked the CPU, so we didn’t have a choice.

Aside from that, not really - we’ve got a c-cms integrated with modx, so we’re probably operating less efficiently than a straight modx installation. But, still considered fast, and handles the load just fine.

Quote from: Starbuck at Feb 28, 2007, 02:00 PM

Turn the counters off :-

administration -> system configuration

Turn-off "log visits" & "resolve hostnames"

Your hosts will be very happy once you have, we use analytics so they’re unnecessary overheads - actually, they cooked the CPU, so we didn’t have a choice.

The flimsy legacy visitor logging scheme does not exist as of version 0.9.5, so you don’t need to worry about it if you’re using that version or above.

I got under 8 requests per second, but that’s a really good result. This site is on a heavily shared server located in the US, which is almost, but not quite, on the other side of the world from where I live.

When surfing, most of the time is spend by reading the content. That’s just being idle when looked from the server side.

Okay. Now I’ve tried the newest MODx 0.95 (before I’ve only used 0.92).

My first question is. I’ve turned on the built in stats, but where is it? Seriously, I’ve been looking for half an hour now - I just can’t find it.

Second question. I’m benchmarking the site now on a testserver and gets about 11 reqs/sec with the default install and default snippets (and example site).
But when I’m using the benchmarktool, I also notice that MODx is generation a LOOOT of Parse-errors, and they all seem to be: "Too many forward attempts".

« Too many forward attempts. »
SQL: The request could not be completed due to too many unsuccessful forward attempts.
[Copy SQL to ClipBoard]

Is this something I should worry about? Can I do something about it, like turn off some reporting features?

Thanks in advance

Remove the template switcher plugin by deleting it; it causes serious problems. There are no longer built in stats because they were slow and buggy.

Quote from: rthrash at Mar 07, 2007, 03:49 PM

Remove the template switcher plugin by deleting it; it causes serious problems. There are no longer built in stats because they were slow and buggy.

Thanks!
I’ve googled on the sql-problem but didn’t find anything. But later found this thread:
http://modxcms.com/forums/index.php/topic,9106.0.html

Okay. So the built in stats are no longer in use. May I just ask why the option is still there to enable it? Is it for 3’d party plugins?

Thanks for a great community. Can’t tell you enough how much I appreciate your work.

Hmm...I’ve deleted the "Template Switcher Plugin" now, and still gets these large amounts of error.

There is another plugin that is core, the "Inherit Parent Template"-plugin. It isn’t that one you mean then? What else could there be wrong if not so? =/

Thanks.

The switches are there indeed for third-party plugins.

Would it be possible to just disable the messageQuit-function in
document.parser.class.inc.php
( http://wiki.modxcms.com/index.php/API:sendForward )

and just redirect the user to another static Error-503 page, or maybe use some other variable to output an customized error?
Or would this break something else?

I also read some solution here also seems to do what I’m thinking - disable the messageQuit-function.
http://modxcms.com/bugs/task/358/edit

What do you guys have to say?