Sorry maybe my question wasn't fully clear the first time. With the option "Simulate new user on each iteration" I expected that for each iteration the browser would be reset and cookies and cache would be cleared, I did not expect that the client machines DNS cache would be flushed. Here is how I came to thsi conclusion...
With the "Simulate new user on each iteration" option set I performed the following test, with 125 Vusers where each Vuser is running the same script and approaching the same URL:
- Flushed the DNS cache on the client machine ( = LG) as to force a DNS lookup at the DNS server by the client.
- Started wireshark on the client machine with display filter on 'dns'
- Started the test
Wireshark now shows very frequent DNS requests all with the same query and the server answers them properly with the correct A record. Apparently for each new Vuser a DNS query is started and also for each iteration a DNS query is started. This last I have verified by tracing again with Wireshark after all Vusers were started: still a lot of DNS request.
Actually I expected a DNS query only once at the very beginning of the test and that it would be stored in the DNS cache. But what I see in the trace is quite different. This leads me to believe that the "Simulate new user on each iteration" setting forces the DNS cache to be flushed at the start of each iteration.
But it is something I would like to see confirmed by an HP expert...
Regards,
Peet