Subject:
|
Re: Sluggish nntp performance
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Mon, 11 Oct 1999 17:17:18 GMT
|
Reply-To:
|
jsproat@+StopSpam+io.com
|
Viewed:
|
339 times
|
| |
|
|
Sproaticus wrote:
> Todd Lehman wrote:
> > As far as I can tell, it's some sort of ISP networking traffic thing...?
> > Pinging www.lugnet.com reports "Request timed out" at the sames times that
> > pinging www.pair.com reports the same, while pinging other sites like
> > www.yahoo.com and www.netscape.com report normal replies. What do you see
> > when you ping?
> traceroute was taken during ho-hum performance; I'll take another one during
> really flaky 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.###.###]
2 <10 ms <10 ms <10 ms #############.###.novell.com [137.65.###.###]
3 <10 ms <10 ms <10 ms #############.###.novell.com [137.65.###.###]
4 <10 ms 10 ms 10 ms #############.###.novell.com [137.65.###.###]
5 <10 ms 20 ms <10 ms Serial5-1-1.GW1.SLT1.ALTER.NET
[157.130.162.77]
6 <10 ms 10 ms 10 ms 137.39.167.101
7 <10 ms 10 ms 10 ms 195.ATM2-0.TR1.SLT3.ALTER.NET [146.188.224.2]
8 50 ms 60 ms 50 ms 113.ATM6-0.TR1.DCA1.ALTER.NET
[146.188.137.209]
9 40 ms 50 ms 51 ms 199.ATM7-0.XR1.DCA1.ALTER.NET
[146.188.161.133]
10 70 ms 60 ms 60 ms 193.ATM8-0-0.GW1.PIT1.ALTER.NET
[146.188.162.81]
11 60 ms 60 ms 60 ms pairnetworks-gw.customer.ALTER.NET
[157.130.32.178]
12 * * * Request timed out.
13 60 ms 60 ms 71 ms lugnet.com [209.68.63.236]
Trace complete.
</TRACEROUTE>
> > p.s. HTTP, unlike NNTP, is stateless, so it's a lot easier for NNTP
> > connections to drop and cause headaches than HTTP. Your web browser might
> > also have higher TCP/IP timeouts or latency tolerances than your newsreader.
> Hmmm... I haven't thought of this. Monday when I'm at work again, I'll put a
> packet sniffer on it and see if I'm getting a lot of timeouts...
I sniffed the session, and I couldn't see any dropped packets. What I *DID*
see, however, is that some ALTER.NET routers take longer to answer than
others, and LUGNET.COM takes about 30 seconds (!) to connect to via NNTP.
After that, it's fairly rapid, delta times being in the one-to-two-digit
milliseconds. This happens against ports 119, 8000, and 8080.
However, the entire front page for WWW.LUGNET.COM came across HTTP (port 80)
within 1.54 seconds.
Does this sound like something in the firewall on my end? Or could it be
ALTER.NET dropping the ball for certain IP traffic?
Cheers,
- jsproat
--
Jeremy H. Sproat <jsproat@io.com> ~~~ http://www.io.com/~jsproat/
Jeremy: "Hi, My name is Jeremy Sproat, and I'm a...Slashdot Lemming."
All: "Hi, Jeremy."
|
|
Message has 1 Reply:
 | | Re: Sluggish nntp performance
|
| (...) 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)
|
Message is in Reply To:
| | 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 (...) (25 years ago, 10-Oct-99, to lugnet.admin.general)
|
42 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
