forum.e-valid.com

Why don't you allow the synchronization logic to run faster than 100Hz, which is only a 10 millsecond interval?

pjg55 wrote:Why don't you allow the synchronization logic to run faster than 100 Hz, which is only a 10 millsecond interval?

It turns out that a 100 Hz gives you timing values to the nearest 0.01 seconds -- 10 milliseconds -- and in web browser terms that is a very small amout of time relative to typical page-load times that are 1 or 2 or 3 seconds or more.

There's really no reason technically why eValid couldn't do the DOM synchronization checking faster, except that you would run the risk of having the synchronization logic take "too much" of the CPU. We basically want to avoid that risk if we can.

Our rule of thumb for this kind of thing over the years has to provide timings that are accurate and do NOT interfere with the behavior of the browser. And a 100 Hz re-sample rate into the DOM appears from our experiments to meet that criteria.

The eValid Team