simult wrote:How many simultaneous monitors do you recommend running?
Even though it is the same test engine used in LoadTest mode and Monitoring mode, there are different constraints and limits and guidelines for each one.
The main objective in Monitoring mode is to make sure that playbacks are reasonably protected from each other...so you don't generate false negative response in the monitoring reporting engine.
For this protective step we generally recommend ten or fewer eValid's in parallel in Monitoring mode.
In LoadTest mode, the more users running the better...but here experience shows that machines run out of resources of all kinds at/beyond 100+ BUs in parallel.
eValid Support