MonoX support board

Start the conversation, ask questions and share tips and solutions with fellow developers.

Non-registered users can only browse through our support boards. Please register now if you want to post your questions. It takes a second and it is completely free. Alternatively, you can log in without registration using your credentials at major sites such as Google, Microsoft Live, OpenId, Facebook, LinkedIn or Yahoo.

How scalable is MonoX with all of the social features enabled?   (Mono Support )

Viewed 11242 time(s), 2 post(s) 11/22/2011 4:26:13 PMby Hewie
Hewie

Hewie

11/22/2011 4:26:13 PM
Hi!

I have downloaded and played with Monox with a view to using it as the basis on an online ecommerce site with social features. I have also looked into other non MS options (ELGG, Plone, DJango etc). MonoX appeals as

1) I like it!
2) it is well documented
3) It uses technology I understand well (I am a C# .net developer by trade).

However....I am concerned about the scalability of the overall solution. I have worked on enterprise web farms with network laod balancers / clusters of SQL servers etc, so I know how hard it can be to make a solution scale.

Can I ask what is the largest site you are aware of using the MonoX social features and how many concurrent users do they support? How much have you load tested MonoX? It looks to me like a lot of the MonoX SQL is produced by LLBGen or LINQ and I wonder what scope there is to tune this if I hit a bottle neck? How many users can hit MonoX with comments / messages / wall posts etc at the same time? Has it ever been installed under Azure?

In previous projects having our SQL in SP's has allowed us to make dramatic performance gains when neccessary. However SQL can still be a bottle neck, hence the drive for NOSQL solutions or database sharding etc. I am concerned about hitting a performance roadblock if I go with MonoX and have little control over the backend SQL.

Many thanks,

Hewie.
This content has not been rated yet. 
16 Reputation 1 Total posts
denis

denis

11/22/2011 6:00:56 PM
Hi Hewie,
We have sites with up to 500-600 k of users that are running on top of MonoX. There are some additional numbers in the tutorial, based on the load testing of a standard site (social networking features included) performed on a single server. SPs can make the difference in specific scenarios (but are much more difficult to work with and maintain), and we are using them when we need to gain evey bit of performance. Nothing prevents you from using SPs with LLBLGen in your custom projects. Additionally, caching is the feature that can bring dramatic improvements, and we use it a lot.

As for the cloud-based infrastructures that are supported, we have MonoX running under Amazon EC2, with support for Azure and AppHarbor in the works.
There are no simple rules here. A lot of time can be spent on optimization (SQL server, indexing, fragmentation, design that supports page-level caching, etc.) - we feel that the base framework gives you a solid foundation you can use to build a scalable solution. BTW, we also like the NoSQL approach - there are some plans to support it in the future.
This content has not been rated yet. 
7207 Reputation 956 Total posts