I’m working on the business case for an application that we intend to write using Meteor. Our portotype is running pretty nicely on a min-requirements dev server (512M/1core) on vultr.com.
But I’ve been wondering how many users you can usually serve concurrently using Galaxy. So if you have some experience and can let me know how many concurrent users you have served using the compact, standard, double and quad containers, that would be really helpful.
About the application
The collections are all indexed on the parameters that are used for publications and publcations usually request only 12-24 items at a time. The most complex pages may subscribe to 2-3 collections. I use paging rather than infinite load to reduce the data stored at any time.
All insert and update functionality is done when the user presses save, so the number of updates are at a rather low frequency and no data is changed at high frequency (through automation).
We expect to have up to 200 concurrent users within 3 months of going live, so I want to make sure that Galaxy can cope with that level and won’t cost us an arm and a leg or might require us to consider scaling horizontally.