// COMPLETE THREAD

List latency.

2 expanded posts ยท every known parent and child

NODE b52111ccList latency.
> 
> At 12:20 PM 10/2/95, Peter Trei wrote:
> 
> >For those curious about the latency, I'm posting this at 12:08, on the US
> >east coast.
> >How long did it take to reach you?
> 
> I got it at 09:14, Pacific Daylight Time, so there appears to be no lag.

Here's the relevant headers for the bounceback to me, which took an hour:

> Received: from relay3.UU.NET [192.48.96.8] by alcor.process.com
>            with SMTP-OpenVMS via TCP/IP; Mon, 2 Oct 1995 13:10 -0400
> Received: from toad.com by relay3.UU.NET with SMTP 
>  id QQzjst04916; Mon, 2 Oct 1995 12:51:05 -0400
> Received: by toad.com id AA00166; Mon, 2 Oct 95 09:10:05 PDT
> Received: from alcor.process.com by toad.com id AA00160; Mon, 2 Oct 95
> 09:10:02 PDT Message-Id: <9510021610.AA00160@toad.com> Received: from thunk
> [192.42.95.240] by alcor.process.com
>            with SMTP-OpenVMS via TCP/IP; Mon, 2 Oct 1995 12:10 -0400
> Date:          Mon, 2 Oct 1995 12:14:30 -6

Translating:

Sent by thunk.process.com                         
12:14 EDT 

Received by alcor.process.com 	
12:10 EDT     -4 minutes (thunk's clock is off)

Received by toad			
  9:10   PDT     0 minutes

Received by uunet			
12:51 EDT     41 minutes

Received by alcor			
13:10 EDT     19 minutes

It looks like there's a considerable delay entering and leaving uunet. I'm not sure which 
machine gets the blame, but it's either toad&uunet, or uunet&alcor.





Peter Trei
Senior Software Engineer
Purveyor Development Team                                
Process Software Corporation
http://www.process.com
trei@process.com
NODE 5dfe9882Re: List latency.
Peter Trei writes:
[...]
 > It looks like there's a considerable delay entering and leaving uunet. I'm not sure which
 > machine gets the blame, but it's either toad&uunet, or uunet&alcor.

sending mail to myself (not going through list processing),
via toad.com, It took 32 seconds for my host to find, contact and send
the mail to toad.com, then it took more than 5 minutes for it to come
back, and specially it came back as :

Received: from relay3.UU.NET by hplyot.obspm.fr with SMTP
	(1.36.108.10/16.2.5) id AA05486; Mon, 2 Oct 1995 19:48:39 +0100
Return-Path: <dl@hplyot.obspm.fr>
Received: from toad.com by relay3.UU.NET with SMTP
	id QQzjtb16149; Mon, 2 Oct 1995 14:47:28 -0400
Received: from hplyot.obspm.fr by toad.com id AA02554; Mon, 2 Oct 95
11:42:59 PDT
Received: by hplyot.obspm.fr
	(1.36.108.10/16.2.5) id AA05454; Mon, 2 Oct 1995 19:42:31 +0100

So the question now is :
 "Why the toad.com send its mail through *.uu.net instead of sending
  it directly ?"

[it would/should cut at least by half the delay {at the coast of more
DNS traffic for toad.com}]

Also I suspect the long delays we sometime see comes from
toad<->uu.net interactions [besides the normal overhead of sending one
mail to thousands of people]

(the service is great anyhow)

dl
--
Laurent Demailly * http://hplyot.obspm.fr/~dl/ * Linux|PGP|Gnu|Tcl|...  Freedom
Prime#1: cent cinq mille cent cinq milliards cent cinq mille cent soixante sept

Chirac Panama Peking Serbian Treasury smuggle Saddam Hussein