ajaxtester wrote:Ok, been studying your stuff.
I like the active DOM synchronization...seems like that is cleaner than some kind of wierd JavaScript passage (if that even works, which maybe I doubt)...
But, what kind of overhead do you incur if you run your sync test at the maximum rate?
(Is the maximum rate for this 100 times per second. Am I reading that right?
That does seem to be very high...)
AjaxTester
In most cases, even if you have the DOM synchronization retry time set
to its lowest value, 10 mseconds (i.e. 100 Hz), you don't see the effect
as long as you are not running 100's of eValid's in LoadTest Mode.
In that case, we generally throttle the rate down to 10 Hz, i.e. an interval of 100 mseconds, but that really doesn't interfere with realism: think about it,
what web application you know of runs as fast as a 10 Hz update rate?
The eValid Team!