walterv wrote:We're seriously considering the eValid solution but some people here don't really believe yoru claims that you can scan 100X and still get realistic playback of test.
Can you explain how that it possible?
We're guessing that you need a really souped up CPU to do this...what do you recommend that we use to get the best price/performance ratio?
Walter VanR
Several points are important to understand here:
(1) Each eValid instance in a LoadTest run is a separate Windows process
with entirely separate execution details.
(2) In LoadTest mode the eValid instances is called "eValidT" -- eValid THIN. This version of eValid has the least possible playback-only footprint.
(3) You probably need 2+ GBytes of RAM to run 100+ eValid instances. Our esperience is that you run out of RAM first, but you soon run out of CPU capacity too, particularly if your applications are very heavy in JavaScript (e.g. if you are running 100+ instances of an AJAX appliation).
So, no you don't need a super-powerful CPU but a "strong one" would
be valuable. Remember: "your mileage will vary" and our results are only suggestions... YOu may be able to get LOTS more than 100...we have seen as many as 250+ in parallel (but with a red-lined CPU, to be sure).
-eValid
