Hello Petar,

Thank you for your inquiry. That sounds like a lot of actively engaged users! What I would suggest is for you to ensure that your machines can cope with such heavy-duty tasks; this you would have to consult your hosting providers.

As for our system, EasySocial can cope with activities as long as Joomla itself can cope with it. With that being said, my personal advice would be for you to consult your hosting provider and ensure that your hardware can meet up with the up-coming traffic.

Hope this helps! Let me know if there's anything more that I can assist you with.

Hi Ahmad,

Just out of curiosity what are the known limits of the Joomla system i.e. with and without excessive tweaking (with the understanding that hardware is not an issue)

Cheers
Avinash

Hello Avinash,

To be honest with you, the limitation is dependent on your server. You can't really say that hardware is not an issue simply because if your current hardware only supports up till 50,000 users before it crashes (overloaded), you then need to upgrade to a better machine. If you have a really good hardware, I would say that it wouldn't be any problems at all hitting the 500,000 users mark.

Hi Mark,

When you say "500,000 users mark" is that the number of registered users or users actively posting concurently?

- For hosting I am looking at Jelastic by Servint (https://www.servint.net/jelastic.php).
- Someone mentioned using Amazon EC2 and Amazon RDS to split the load
- Seems that consensus is that Nginx is better option to Apache.

Also, do you have any suggestion on hardware - you seem to have a pretty active community yourself here.

subscribe++ to the discussion

Hello Petar,

I am actually referring to 500,000 registered users. As for the number of concurrent users, to get 500,000 users actively logged in and accessing the site at the same time, you need to really have a super solid server running. Perhaps you probably need a couple of servers and you also need to consider adding load balancers to ensure that the loads are spread across multiple servers.

Thanks Mark,

I was afraid software wouldn't be able to handle such a setup / user load - hardware seems to mostly come down to the money and the right workflow.

I came across this on another Joomla forum (thanks to Steven Koontz for sharing)

I changed all DB table engines to InnoDB (except the two finder tables _finder_tokens and _finder_tokens_aggregate which are supposed to be MEMORY tables). No problems. No performance difference, either. I have index hints turned off, but a quick test didn't show any difference with them on, either. Note that Joomla 3 uses InnoDB by default. I also saw that K2 now adds InnoDB tables on new installs instead of MyISAM which they used previously. All of my extensions were using MyISAM (EasySocial, EasyBlog, NoNumber, Admin Tools, Akeeba Backup). However it seems Joomla core has made the move to InnoDB.

I have seen zero performance difference. Amazon guarantees 100 IOPS for "normal" RDS instances like mine, which is also what they guarantee if your MySQL is on your EC2 webserver. My site with 1500 unique visitors a day very rarely tops 50 IOPS. My main reason to move to RDS was to take some strain off the main nginx webserver. It is amazing the reduction in CPU and memory usage by offloading MySQL to its own RDS server. The nice thing about this setup is:

1) DB created as private instance and placed in same VPC as the EC2 instance. Only the EC2 webserver can access it. The DB itself cannot be accessed by anything outside the VPC.
2) Offload the most intensive part of Joomla (the DB queries) to a dedicated, external, MySQL server).
3) Easy resizing: Both EC2 webserver and the RDS DB can be easily resized as need be as traffic increases.
4) Automatic backups

Is switching to InnoDB something one should entertain for ES or keeping everything standard is good enough?

Would this type of set up work for in case?

Subscribe

Hello Petar,

There are pros and cons for utilizing innodb and you can actually view it here, http://www.sitepoint.com/mysql-innodb-table-pros-cons/ . If I recall correctly, Joomla 3.x by default uses Innodb already.

Hi guys,

Good thread.
Is there any limit line (active at the same time users) after the site located at a shared hosting (like Hostgator etc.) starts crashing?
Thanks

Subscribed.

Hello Filatov,

There's really no "exact" answer because it all depends on how much traffic is the entire server serving. If the hosting provider oversells, then you'll most likely hit issues when it comes to more traffic.

Also, do take note that when you purchase shared hostings, it all comes with a very tiny "terms and condition" and they did actually state that you are only allowed to consume specific amount of cpu allotted to your account.

Just subscribing... excellent topic!

Yes, it is.