You can include an aggregate report to your test plan. In your actual Login request you can add a Duration Assertion so that the step fails if it passes a certain acceptable time. Then you set up different runs with different concurrency levels and check that your error percentage remains low through each test.
For system sizing you will have to monitor the system as well to see when resources are exausted adn determine possible bottlenecks.
Assume is not really the word you want to use when reporting.
What information did you get from the monitoring logs?
What is the status of the box when it was running at 10 users concurrently? And then when running 20 and 25? All of these together will give you an answer of why your getting these failures.
oh Thanks a lot...that really helped. [img]/images/graemlins/laugh.gif[/img].... I am facing another problem.... which is .. I have included the csv data config. but each time its taking the 1st valiue. I have assigned variables correctly. can anyone tell me what is the way to get all the data one after one in each iteration...or each thread request?