How many site contexts supported in Revolution?

I was wondering if anyone could give me input on any limitations that might exist for site contexts in terms of Manager hard limits or performance limitations.
Is it realistic to expect ModX to handle hundreds of domains as contexts inside of one install? These would all be low volume in terms of traffic and content.

Thanks,
-Brian

I think it’s all down to usability in the end.. I think MODX can handle it, but do you want a list of 100 contexts in your navigation tree? MySQL might also have a limit somewhere (although from 2.1 on you should be able to use selected other database systems too).

What you also have to realize is that your main index.php is going to be delivering all your pages/resources. 100 sites which each get 5 pageviews an hour means 500 requests to the index.php every hour, or almost 9 per second. If some sites suddenly kick off, that can skyrocket.

Clearing the site cache clears the cache for all contexts iirc, so that will also put a strain on your server when that is being regenerated for 100 contexts (although 2.0.8 improves caching big time).


Just my $0.02 based on some theory and my gut feeling about this system. Haven’t tried it yet.

Quote from: Mark at Feb 24, 2011, 06:16 AM

What you also have to realize is that your main index.php is going to be delivering all your pages/resources. 100 sites which each get 5 pageviews an hour means 500 requests to the index.php every hour, or almost 9 per second. If some sites suddenly kick off, that can skyrocket.

I’m just working out how to setup revo for multiple sites and have been deliberating whether to use multiple contexts on one install or would it be better to used the advanced install? So all the sites have their own context but behind the scenes it uses the same core directory? At the moment I’m thinking that the advanced install is the better way to go but would be interested to know if there are any drawbacks with this solution.

Adrian

I think the typical application of using contexts involves putting the MODX core out of webroot where different virtual hosts can access it, and there’s one manager featuring many contexts for the different sites.

So that’s not two different solutions as you put it, but one way of doing. Advanced install which runs multiple contexts.


You can also use one regular install with contexts for site translations, that doesn’t need advanced as it’s all on one domain usually.