Avalanche: How are level 1 and level 2 HTTP requests are handled by SimUser clients and how to configure parallel GET requests / TCP connections per SimUser.
Knowledge Base - FAQ
Avalanche: How are level 1 and level 2 HTTP requests are handled by SimUser clients and how to configure parallel GET requests / TCP connections per SimUser.
For level 1 URIs the first URI must first get a response or timeout before the next level 1 URI is attempted.
When using level 2 URIs if the client/profile HTTP:Browser settings allow multi connections per SimUser you can configure parallel GETs issuing at the same time.
Example:
1 GET http://192.168.1.1
2 GET http://192.168.1.1
2 GET http://192.168.1.1
2 GET http://192.168.1.1
The level 1 GET will require an HTTP '200' server response before issuing parallel gets to the remaining level 2 URIs when the Client/Profile HTTP:Browser settings are configured for 1 request per TCP connection and 4 connections per SimUser.
A common use case for this would be to simulate browser behavior with the level 1 object representing an index.html page and all level 2 requests representing objects within the index.html page such as .jpg images.