Total Number of Concurrent Users Before Performance Degradation

Total Number of Concurrent Users Before Performance Degradation

  

Hi!

I have a question. As the title states, how many concurrent users can a particular environment or webapp take before there is any noticeable performance degradation.


I have seen this: https://www.outsystems.com/forums/discussion/15171/connection-pooling-in-outsystems-platform/


But it does not really give me the info I need. Can I change the max number or connections? Is there a license I have to purchase? What if our user requirement is to have 100 concurrent users without any performance degradation? How can I make sure that it will happen?


Thank you!

Hi Michael,

I do not think there is a straight forward answer, because there are several things to consider in your question.

1) The decrease of performance can be caused by several factors.

2) When you think about the limit of users, for the number of connections you have, do not forget also the connections made by background processes (BTP).

3) You can have approaches to distribute your pool of users per front end servers.

Finally, in case you scale up the servers, probably you'll need to purchase/upgrade your OutSystems licence.

Marco Arede wrote:

Hi Michael,

I do not think there is a straight forward answer, because there are several things to consider in your question.

1) The decrease of performance can be caused by several factors.

2) When you think about the limit of users, for the number of connections you have, do not forget also the connections made by background processes (BTP).

3) You can have approaches to distribute your pool of users per front end servers.

Finally, in case you scale up the servers, probably you'll need to purchase/upgrade your OutSystems licence.

Thank you for the response. From your experience, how much would you say is the number of concurrent user we can promise a client if we have an enterprise subscription?


Good Question ! Michael I am quite interested on the answer if some could help us :)



Hi Michael,

An enterprise subscription allows to scale unlimited. Meaning you can add capacity to your pooling, and scale your application as needed. This information is available in: https://www.outsystems.com/pricing-and-editions/

But of course not all applications will be increasingly performative while scaling, because other perks might lead to an unresponsive system, as for example a poor architecture design. There is an article that provides interesting insights: https://www.outsystems.com/blog/low-code-scales.html

To understand how many concurrent users uses connections pooling, the calculations can be read in: https://success.outsystems.com/Support/Enterprise_Customers/Maintenance_and_Operations/Connection_pools_in_OutSystems_Platform

Resuming, the answer is unlimited... but it depends on several factors. Then you can only have a guaranteed number if you perform stress tests, as in a real world scenario.

Marco Arede wrote:

Hi Michael,

An enterprise subscription allows to scale unlimited. Meaning you can add capacity to your pooling, and scale your application as needed. This information is available in: https://www.outsystems.com/pricing-and-editions/

But of course not all applications will be increasingly performative while scaling, because other perks might lead to an unresponsive system, as for example a poor architecture design. There is an article that provides interesting insights: https://www.outsystems.com/blog/low-code-scales.html

To understand how many concurrent users uses connections pooling, the calculations can be read in: https://success.outsystems.com/Support/Enterprise_Customers/Maintenance_and_Operations/Connection_pools_in_OutSystems_Platform

Resuming, the answer is unlimited... but it depends on several factors. Then you can only have a guaranteed number if you perform stress tests, as in a real world scenario.

This information is very helpful. Thank you!

I do have one last question? If we need to "add capacity to your pooling", will it cost us more?