BarbaraN wrote:Good Morning:
How many instances of eValid do you recommend to run in parallel in monitoring mode?
Thanks very much
BarbaraN
Good afternoon and thanks for asking BarbaraN.
There is a trade-off between use of main memory to run copies of eValid in "monitoring mode" and the effect doing that has on the measured times.
As a point of information, eValid imposes no limit on the total number of copies running at one time. As long as your scripts don't interfere with each other (e.g. try to visit the same website at the same time) then the only limitation if RAM and CPU resource.
But to be honest, we have already found that on relatively slower machines the amount of overhead that is introduced by eValid begins to exceed the 1% threshold that makes engineering sense when the total number of eValid instances exceeds 100.
In other words if you run a safe 10 parallel eValid copies you will be unlikely to see a measurable difference in response time.
Here are two pages from the documentation that may be of interest:
http://www.e-valid.com/Technology/White ... acity.html http://www.e-valid.com/Products/Documen ... index.htmlThe safe number, to repeat, is 10 in parallel. That ought to be a sufficient scaling factor for most cases.
-- eValid Support