I just asked about capacity isses in terms of server loading...that is a different post...

But I also have a concern if I want to provision a lot of parallel eValid instances to run functional demonstration/monitoring type check?

What's your experience in that case?

-SK

You've asked about capacity for monitoring with parallel evalid instances.

You should be OK on this. You can launch any number of eValid instances --
eValid imposes no limits.

Practically, however, you can expect up to hit machine capacity limits at about
100 or slightly more on a standard XP machine.

But for monitoring, you DO -- very important DO here! -- have to make sure that
no two of your parallel executing scripts interfere with each other.

We've seen that happen, usually due to server side settings over which eValid
has no control. An example is, sometimes servers deny you the right to log in a
second time on the same machine, so if you have two scripts in parallel both
trying to do that, you may have a problem because the first one of them that
runs will block the second one.

There is a Lock/Unlock MUTEX available with eValid but using that will
effectively serialize the desktop use between playbacks that you otherwise would
be running in parallel.

As you can guess, this can be complicated when there are funny interactions, but
with care you should be ok for 25 to 50 parallel monitoring tests.