back to the top
- You must configure a warm-up period to permit the application to compile and to cache. If you do not configure a warm-up period, the report shows artificially low responsiveness. This does not accurately reflect the behavior of the application under typical use.
- You must enable cookies, but do not record them as part of the script. This makes sure that each virtual user who is simulated by the WAS tool initiates a separate ASP.NET session.
- You must enable random delay. This prevents requests being sent to the server faster than the events can be processed.
- You must configure the WAS tool to run for several minutes. This makes sure that sufficient requests are processed to generate useful statistics.
- Install and then run the WAS tool.
- Create a new script.
For information about how to create scripts, see the WAS tool Help files.
- In the Microsoft Web Application Stresswindow, expand your script and then select
- Set the Stress Level field and the
Stress Multiplier field to
- Set the Test Run Time to
10 minutes or more.
- Select Use Random Delay. Set the
Min field to 2000 or more if pages take longer than two seconds to run.
- Set the Max field to
- Set the Warmup period to at least
1 minute to permit time for ASP.NET to compile and then cache the application after the first request.
- Click to select the Users, Passwords, And Save Cookies check box.
- Create and then run the script by using any of the standard methods. To do this, see the WAS tool Help files.
- On the View menu, click
- Expand your report item of the script and then select the most recent time.
The right pane displays a summary of the report.
- Move to the Page Summarysection.
For each page in your script, examine the
Hits, the TTFB Avg column, and the
TTLB Avg column.
The Hits column shows the number of requests that are executed against that page. The number of hits must be greater than 10. This makes sure that sufficient requests were issued to generate a useful average. If Hits is less than 10, increase the Test Run Timefield in the script settings and then reexecute the script.
TTFB Avg column measures the average time (in milliseconds) that the application took to return the first byte of the ASP.NET page. This measurement reflects the time from the request that the user issued to the time when the browser of the user starts to render the page. This is the most significant server-dependant factor in the perceived speed of the site. This measurement relates closely to the time that it takes for ASP.NET to render the page. This measurement also reflects configuration changes that affect performance.
The TTLB Avg column measures the average time (in milliseconds) that the application took to return the last byte of the ASP.NET page. This measurement reflects the time from when the request is issued by the user to the time that the whole page is downloaded. While browsers typically start to render pages after they receive the first byte, the whole page is not visible until after the last byte is transferred.
back to the top
Article ID: 815161 - Last Review: Mar 24, 2009 - Revision: 1