CAngelo wrote:What is the ACTUAL overhead due to system factors when you are running 100 browsers in parallel?
There are two factors here: (1) total system time consumed by the browser as the work; and (2) the amount of RAM they use.
Let's deal with these in turn.
(1) By design, each eValid instance is designed to have < 0.1% system overhead time, so at worst
you would see 10% of the CPU lost to system overhead. In practice, however, we have rarely
seen the system time exceed 3%.
(2) The longer the browser run, the larger the footprint. We have seen eValid instances run up to 250 MB of RAM as they browse and browse and browse. But this is not unusual at all. The same thing happens with IE.
If you don't have enough RAM then there is an option in the eValid settings to have the browser respawn (auto-restart) after a specified number of playbacks. The playback time cost for this is 1-5 seconds -- it takes the THIN version about that long to load, but in our experience that has not been a problem.
eValid Load Support Team