forum.e-valid.com

Afternoon.

Why do you set the interval for a synchronization test retry to 10 msec?

What if I want to have it be 1 msec?

Thanks

JJJones wrote:Afternoon.

Why do you set the interval for a synchronization test retry to 10 msec?

What if I want to have it be 1 msec?

Thanks

That is a good question and we will try to give you a good answer JJJones.

Yes, the minimum Retry Interval is set on this page of preferences:

http://e-valid.com/Products/Documentati ... ation.html

The number you enter is the number of milliseconds (msec) used between attempts to synchronize in any of the auto-synchronize commands.

If you put in a number less than 10, you get an error message denying that request.

The effective minimum is then, as you have found out, is 10 msec.

What is this?

Here is the reasoning:

First, recognize that a retry interval of 10 msec implies a retry rate of 100 retries/second.

That means that the interval between retries is 0.01 sec (yes, that's 10 msec).

If you look at typical web pages, even on a very fast (e.g. 100 Mbps) connection and a very fast PC, that length of time is "short" compared with the download and render time of all but very small web pages.

Our thinking is, having the rate go any faster would be wasted effort -- you would not gain anything.

There is, in addition, the client-machine loading factor.

At rates higher than 100 Hz (corresponding to 0.01sec = 10 msec retry intervals) you tend to have your client machine spend more time doing synchronization steps then you do having it download the pages you are trying to synchronize.

That is, going faster would clog your playback engine. And you don't want that do you?

-- eValid Support