KellyL wrote:Good morning.
How does eValid handle cookie and cache contents during multi-playback load testing?
Thanks for posting KellyL.
As you may know and understand, eValid can run multiple copies of itself on a single machine to impose load on a server with minimal machine resources.
The way eValid copies keep from interfering with each other is a feature in LoadTest mode that allows each browser to run without cache and without cookies.
Effectively, each new URL downloaded into any browser is flushed from the cache after it has been rendered by the browser.
Two parallel-executing eValid copies thus always have their own copy of any particular URL.
The same is done with cookies: they are flushed as soon as they are set.
This way, each eValid appears to the server as a lazy client, never storing a URL (and always asking for it afresh if needed), etc.
There are two commands that are also available to you in your script to accomplish this:
Also, you may be interested in this manual page describing how you can adjust the settings relating to cache and cookie management: http://www.e-valid.com/Products/Documen ... ement.html
-- eValid Support