 | | 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)
|
| |
 | | Re: Sluggish nntp performance
|
|
(...) "mtr" == "mean time to reply" or some such? Sounds useful -- I'll track one down. (...) Heh -- More fiber == less congestion. f-up this line to off-topic.pun please. :-, Cheers, - jsproat (27 years ago, 10-Oct-99, to lugnet.admin.general)
|
| |
 | | Re: Sluggish nntp performance
|
|
(...) traceroute was taken during ho-hum performance; I'll take another one during really flaky performance. <PING> c:\pub>ping lugnet.com Pinging lugnet.com [209.68.63.236] with 32 bytes of data: Reply from 209.68.63.236: bytes=32 time=60ms TTL=244 (...) (27 years ago, 10-Oct-99, to lugnet.admin.general)
|
| |
 | | Re: Sluggish nntp performance
|
|
I get: Tracing route to lugnet.com [209.68.63.236] over a maximum of 30 hops: 1 2 ms 1 ms 2 ms zaphod [192.168.0.42] 2 1221 ms 1293 ms 1041 ms autodial-gw1.uk0.vbc.net [194.207.0.56] 3 1292 ms 1299 ms 274 ms lg1.uk0.vbc.net [194.207.0.40] 4 157 ms (...) (27 years ago, 10-Oct-99, to lugnet.admin.general)
|
| |
 | | Re: Sluggish nntp performance
|
|
(...) I rarely notice any trouble, except sometimes posting takes several seconds... (27 years ago, 9-Oct-99, to lugnet.admin.general)
|
| |
 | | Re: Sluggish nntp performance
|
|
(...) Yeah, I've noticed this, especially the last several days. I've also noticed slowness in general on the net, especially in sites that I go through Sprint or BBNPlanet to get to. But at times when everything else has seemed slow, nntp (...) (27 years ago, 9-Oct-99, to lugnet.admin.general)
|