softqa wrote:When you run a loading test with a large number of browsers all running in parallel, how do you know that the don't interfere with each other in some negative way?
Two (or more) instances of eValid each run as separate processes in Windows. There are two areas where multiple eValid instances could interact:
(1) Desktop contention -- where two playbacks each try to access the Windows desktop at the same time. The solution here is to use Lock/Unlock commands so that any one instance has exclusive access to the desktop when it needs (but not otherwise, hence the Unlock command).
(2) Cached material -- where two playbacks try to rely on some file that is in the cache, including a cookie in the cache. The solution we have found that works best is to run multiple-instance sessions withOUT the cache.
True, this may make one or more eValid instances work a little harder because they have to re-download a page that was already downloaded in that playback. It's more work for the browser, but that means really only that the performance results you get are a little more conservative than they would be otherwise.
We hope this answers your question.
--The eValid Team
by softqa » Mon Jan 25, 2010 5:06 pm