[EMAIL PROTECTED] writes:
> I am seeing negative latencies of up to 1 second. I am using ntp to
> synchronize both machines at an interval of 2 seconds, so the clocks
> should be very much in sync (and are from what I have observed). I
> agree that it is probably OS, perhaps I should hop over t
[EMAIL PROTECTED]
> I am seeing negative latencies of up to 1 second. I am using ntp to
> synchronize both machines at an interval of 2 seconds, so the clocks
> should be very much in sync (and are from what I have observed). I
> agree that it is probably OS, perhaps I should hop over to a Micro
I am seeing negative latencies of up to 1 second. I am using ntp to
synchronize both machines at an interval of 2 seconds, so the clocks
should be very much in sync (and are from what I have observed). I
agree that it is probably OS, perhaps I should hop over to a Microsoft
newsgroup and pose th
What makes you believe that the two machines' clocks are perfectly
synchronized? If they're not, it easily explains the result.
I wrote a simple client/server program similar to what you described.
Running on two RedHat 9 machines on a local network, I generally
observed a time delta of 2ms (comp
Python version is 2.3.3. Using Windows XP SP2 as stated above.
Network infrastructure is really irrelevant, what I'm attempting to
figure out is how a time.time() call on another machine that occurs
AFTER a message is received could occur before the message is actually
sent.
--
http://mail.pytho
I've just noticed that you didn't mention any details like OS, versions,
network infrastructure. You do not mention either how large the difference
is.
Andreas
--
http://mail.python.org/mailman/listinfo/python-list
At least on the order of .1-1 seconds. Both platforms are Windows XP
SP2.
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] wrote:
> I am working on some code using python and a distributed system. Some
> particular message is sent on one machine (with a timestamp logged) and
> after the message is received, a timestamp is made. I am having
> problems with negative latencies happening under intense C
I am working on some code using python and a distributed system. Some
particular message is sent on one machine (with a timestamp logged) and
after the message is received, a timestamp is made. I am having
problems with negative latencies happening under intense CPU load.
There is ntp sync happen
