Hey,

We've been getting good results from you dynamic synchronization -- works great, cool feature.

Big question here is, how much overhead is this eating? We need to have confidence that even though our tests are completing every time without difficulty we are not skewing the data because eValid takes too much time doing the synchronization work.

What say?

CTEST21

Yes, the AJAX synchronization logic is pretty cool. Thanks
for the compliment.

The performance issue is an important one because you don't
want the overhead from doing the synchronization to interfere
with the AJAX work being done with the JavaScript engine.

Remember that eValid is a "direct execution" type
implementation, so these internal synchronization loops are
done in C++/CPP directly within the browser. As a result of
this architecture the timing overhead is minimal, in most
cases not even measurable.

But we feel safe saying that the overhead is less than 0.1% of
the total time. That's less than 1 part in 1000, and we hope
that is accurate enough.

In most cases, the sync process does not appear to have any
performance degradation penalty at all.

Here is a short explanation page for how these powerful eValid
commands work:

http://www.e-valid.com/Products/Documentation.9/DOM/adaptive.sync.html

Adaptive DOM Synchronization Explanation

--The eValid Team