 | | Re: Sluggish nntp performance —Jeremy Sproat
|
| | | (...) 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 (...) (25 years ago, 10-Oct-99, to lugnet.admin.general)
|
| | | |
| | | | | Re: Sluggish nntp performance —Jeremy Sproat
|
| | | | | (...) 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.###.###] (...) (25 years ago, 11-Oct-99, to lugnet.admin.general)
|
| | | | | |
| | | | | | | Re: Sluggish nntp performance —Jeremy Sproat
|
| | | | | | (...) Followup: Performance today is stellar. Here's a traceroute: <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.###.###] 2 <10 (...) (25 years ago, 15-Oct-99, to lugnet.admin.general)
|
| | | | | | |
| | | | | Re: Sluggish nntp performance —Scott Smallbeck
|
| | | | 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 (...) (25 years ago, 11-Oct-99, to lugnet.admin.general)
|
| | | | |
