Hardware Costs

[misjan]

We ended up actually rolling a custom framework to be able to scale to the
number of clients we needed. We determined that using eValid we would simply have to purchase way more hardware than would be feasible to test with a few hundred clients, as the javascript portion of our GWT app is too much of a CPU burden running in a full IE environment for each client.

[serverloading]

Understand and thanks for the explanation.

Actully, the 100X scale factor works fine with heavy AJAX
applications but does ask for a hefty CPU. We don't see an
appreciable slowdown except if you remove ALL of the wait time
(that is as long as you keep the duty cycle < 25% or so).

And, at < $1/hour for an XP image on the cloud...hardware costs
are becoming a non-issue.

(We have a press release on this coming out in a week or so;
we'll be offering eValid instances on the clout for a very
lost cost per test...).

Hardware is inexpensive; labor costs are the killer. eValid reduces
the labor costs to nearly zero, and if you put in a few extra bucks
for hardware you're well ahead of the game.

Let me know if you want to go around again.