Appboard/2.4/admin/performance and sizing
Revision as of 10:46, 28 August 2013 by imported>Jason.nicholls
On the recommended hardware enPortal should support 100-200 concurrent user sessions depending on how active / how many simultaneous requests are made overall.
For AppBoard the situation is quite different due to the AppBoard server caching and processing data. This can be heavily influenced by the size of data-sets, caching times, client polling frequencies, and the miscellaneous ways to transform data such as sub-queries, filtering, and data processing scripts. For a moderate deployment the number of concurrent users may be in the range of 50 or so but could vary greatly.
As a general rule when it comes to tuning it's critical there is sufficient memory allocated to enPortal/AppBoard or CPU time will increase greatly. If there is sufficient memory, or memory capacity is exhausted, or CPU is exhausted then the way to scale is via load-balanced clustering.
