java - What is a good standard metric for stability in a web application? -
We are currently experiencing some stability issues with the development of our web application product. This product was made in part by our partner contractor, and we want to keep a good standard metric for stability. The problems we are facing are constantly crashing. The web application is unable to recognize that when it is handled, more requests are made, it creates memory (such as memory leakage) and later it dies without any possible recovery.
We want to write a very simple measure to meet our partner contractor. We thought of some ideas:
- A system which is capable of identifying the high load of the request and making the server unavailable, again try the pages again, as long as it High loads are not cured.
- A fixed number of users of concurrent or pageviews that allow us to have a clear metric of using scalability options like load balance and caching.
Caching us at this time and
Thank you for your help.
"high load" really defined It's hard to do
It is very easy to determine whether you are the lowest acceptable service level.
-
Minimum number of concurrent requests
-
Maximum time to make a request.
Any lawyer or accountant can review the results of the load test and say that they did not have minimum or minimum, no intense technical knowledge is necessary.
Note that when you do this, "minimum is maximized" if you say that they have to meet minimum 10,000 requests per hour, your test will often tell that the maximum is also .
So define your minimum and maximum points with your business model. How many people do you need to keep people happy and productive? Ask for more is silly ask for unhappy or unproductive users with fewer means.
Comments
Post a Comment