We were unable to locate this content in de-de.
Here is the same content in en-us.
Start EarlyDefine Your EnvironmentDefine Your Testing StrategyBut How Many Users?Know Your MetricsInterpret Your MetricsChoosing the Right Load Testing ToolKnow Your HistoryConclusion
As an alternative, we suggest you design your test cases around these key questions:
To answer the stability question, run a test to sustain a reasonable number of concurrent, unsynchronized super users for an extended period of time. We used overnights and 24-hour periods on our last project, but the duration is application dependent. We refer to this as a "burn-in" test. Once you've taken steps to identify and potentially resolve the bottleneck found, repeat the synchronization point test to see if the lower limit has increased. Then rerun the "burn-in" test with the new number for concurrent users supported. Repeat this cycle with the goal of striving to improve upon this number until the quality bar is reached.Don't Use Your Dev Environment for Load Testing
For background information see:ScalabilityPerformanceThe Art and Science of Web Server Tuning with Internet Information Services 5.0
More MSDN Magazine Blog entries >
Browse All MSDN Magazines
Subscribe to MSDN Flash newsletter
Receive the MSDN Flash e-mail newsletter every other week, with news and information personalized to your interests and areas of focus.