 | | Re: Sluggish nntp performance
|
|
Larry Pieniazek <lar@voyager.net> wrote: [snip] (...) [snip] (...) In both of these cases, you're having trouble before you even get out of psinet. That makes the rest of the data irrelevant.... (27 years ago, 11-Oct-99, to lugnet.admin.general)
|
| |
 | | Re: Sluggish nntp performance
|
|
My subjective observation is that performance is definitely deteriorating.... Here are a couple of tracerts... I have blanked out the first two network addresses, my client is confidential. But with times under 10 ms they may or may not matter much. (...) (27 years ago, 11-Oct-99, to lugnet.admin.general)
|
| |
 | | Re: Sluggish nntp performance
|
|
Time to connect is now up to 38 seconds. Doesn't seem to ever be better or worse, consistently 30+ seconds. Tracert looks pretty good, 6 alter.net routers to pairnetworks and they pass through very quick. Losing about 10% of the packets pinging (...) (27 years ago, 11-Oct-99, to lugnet.admin.general)
|
| |
 | | Re: Sluggish nntp performance
|
|
(...) traceroute taken during bad performance showed about the same times. <TRACEROUTE> c:\pub>tracert lugnet.com Tracing route to lugnet.com [209.68.63.236] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms ###...###.###.novell.com [137.65.###.###] (...) (27 years ago, 11-Oct-99, to lugnet.admin.general)
|
| |
 | | Re: Sluggish nntp performance
|
|
(...) "mtr" meaning "Matt's traceroute", I believe. (Not me; Matt Kimball) It's basically a fancier traceroute/ping program. (27 years ago, 10-Oct-99, to lugnet.admin.general)
|