Adjusting delays in HTTP tests
You can configure HTTP tests to use client-side processing
delays. Client-side processing delays wait for the first character
or last character that is received in a response for a previous request
in order to better emulate the work done on the client computer. You
can also scale the recorded delays in HTTP tests to change the rate
at which a test runs.
- Configuring HTTP client delays
You can configure delays for HTTP requests to emulate client-side
processing delays. Applications that use client-side Javascript, such
as Web 2.0 applications, often incur significant delays due to processing
done on the client. You can emulate this client-side processing in
HTTP tests. Running an HTTP test too quickly can cause unexpectedly
low page response times to be reported, and can generate excessive
load on the server under test.
- Overriding the HTTP connection timeout value
By default, HTTP page connections use a timeout value of
190 seconds, which might not be sufficient for some applications.
You can override the page connection timeout value for specific pages
in a test.
- Playing back HTTP tests faster than the recorded rate
If the client computer used for recording an HTTP test
was slower than required, or if you want to emulate a faster client
computer, you can increase the playback rate without altering the
actual values in the recorded test by reducing the client delays proportionately.
Similarly, you can slow down the client by increasing the client delays.