Scalability testing is a series of performance test that measures different hardware and software configurations of an application with the goal of finding what key indicators of performance failures will tell us when we need to add more disk space or more servers to our environment...
User Avraham Melamed (email@example.com) posted:
It means (IMHO) something like:
1. If your application works OK with 5 rows for each table in your database,
will it also work with 5 million rows in some of the more critical ones?
If not, your application does not scale up.
2. If your application works OK with 5 million rows in the some of the
tables in the database but it takes it 3 minutes to bring a form when there
are only 5 rows in those tables in the database then the application does
not scale down real well.
Other folks may fill in other blanks in this concept.
Scalability testing is done in order to undestand the following questions and many more:
• What kinds of satisfaction levels will your customers have when they use your site during normal operation, and is that different from at a 'rush' hour?
• If your web application front-end integrates with legacy applications, what impact will this new traffic have on those back-end systems?
• Will your system meet the overwhelming demand created by your marketing and promotional programs?
my quote - "your actions should proove beyond all doubts"
Most common question asked is 'Is the appliation scalable?'. Most developers will tell that, what is implied in this question is whether the arhitecture on which the application is built supports increase in number of users or inrease in traffic and still maintain good performance.
[This message has been edited by nageshsm (edited 01-23-2003).]