Can MODx handle high traffic site (average 1600 requests per second, see graph)?

I have a site currently getting 1600 requests per second (see server stats attached) with peaks of 3300+



Can MODx handle this? In particular, I would like to know:

1) How many queries does MODx make to create a page on average?

2) Does MODx have full and fragment caching?

3) Does MODx support Varnish cache? (varnish-cache.org)

Let me know, I am considering migrating to MODx but I hear conflicting reports on its scalability

What is that, facebook?

I’m not the one who can answer your question, but I imagine one of the core devs will respond soon enough. I’m interested to hear what they say.

But out of curiosity which CMS are you currently using to handle that much traffic, if not a custom built solution?

OK this doesn’t answer the question, but could I ask are you sure it is 1600 a second those graphs show 5min and 30min averages of that amount not per second. Or am I reading them wrong if I’m not then the figures should be.

1600 /5 = 320 per min
320 / 60 = 5.33 per second.

If this is really the case then I would say it is doable, but again I’m sure the core would have a better answer.

Is this serious?

Some thoughts:

With 1600 requests per second on my pages, i would not worry about the scalability of MODx Revolution.
I would worry about the scalability of my hardware/bandwidth and infrastruture.

No well written software can handle this alone.

Not every request of a "1600 requests per second" site calls dynamic content.. and if thoose stats actually do show calls on dynamic content, then... i’m feeling fuzzy.

Again, is this seroius?

But out of curiosity which CMS are you currently using to handle that much traffic, if not a custom built solution?

It’s just Wordpress running on Nginx (no Apache) with WP-Cache plugin so that every page is served statically.

OK this doesn’t answer the question, but could I ask are you sure it is 1600 a second those graphs show 5min and 30min averages of that amount not per second. Or am I reading them wrong if I’m not then the figures should be.

1600 /5 = 320 per min
320 / 60 = 5.33 per second.

That’s not right because the 1600 figure has already been divided by the number of seconds in five minutes. And if you still think its 5,33 requests per second, check Linux snapshot:

netstat -an | grep 80 | grep ESTA | wc
1576 9456 140264

The first number indicates concurrent connections.

No well written software can handle this alone.

Any software with a lite server (such as NGINX) and *full caching* (such as Varnish) can handle this very easily.

I am (was?) interested in MODx because I read that it has (had with Evolution? not anymore with Revo?) a modest (5-7 queries) number of queries per page. If MODx has a low number of queries per page and good native caching, then it could notify Varnish that a certain content has been updated or changed so that the cache is purged and recreated as needed.

Drupal (infamous for making a TON of queries) has found a way to scale with a Varnish Module http://blogs.osuosl.org/gchaix/2010/01/20/varnish-drupal-module-first-impressions/ that does this.

Integration with Varnish Cache will give MODx a terrific ability to cope with high loads with very modest hardware, check it out: http://www.varnish-cache.org/ Varnish is just awesome, it’s free and open source - it would be a mistake not to embrace it.

Node.js + mongodb

Check em out.

Quote from: webfusion1 at Jun 12, 2011, 08:39 PM

But out of curiosity which CMS are you currently using to handle that much traffic, if not a custom built solution?

It’s just Wordpress running on Nginx (no Apache) with WP-Cache plugin so that every page is served statically.

MODx Revolution caches pretty much everything.
IMHO if WP runs well, MODx will run very smoothly.
And if you want to avoid php-processes at all when serving your frontend-pages, just use my Statiker-extra for MODx Revo to render thoose "can be served staticly" pages into good old static files.

Why are you posting from two different accounts Webfusion/webfusion1 (with what looks to be generated email addresses)?

To answer your question on caching, I think MODX will scale quite well for you in it’s core form, but you may want to extend the caching to work with your favorite caching mechanism (Varnish). I"m sure Jason’ll chime in on this topic soon enough.

Quote from: rthrash at Jun 13, 2011, 08:11 AM

Why are you posting from two different accounts Webfusion/webfusion1 (with what looks to be generated email addresses)?

Here here, this looks like an information gathering exercise for one of them silly "My CMS is better than yours because...."

Does anyone know if someone has built a plug-in (or some sort of MODx add-on) that integrates Varnish Cache?

Website: htp://www.varnish-cache.org