Subject:
|
Re: Sluggish nntp performance
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Fri, 8 Oct 1999 21:50:17 GMT
|
Viewed:
|
213 times
|
| |
|
|
In lugnet.admin.general, Jeremy Sproat writes:
> Has anyone seen slow performance from LUGNET's nntp server? The http
> server is very fast and nimble, etc. but whenever I connect via nntp,
> it's always slow and sometimes dropping the connection, whether I use
> port 119, 8000, or 8080.
Something really net.weird is going on today, but I don't see special
notices at Pair yet:
http://support.pair.com/notices/
What I'm seeing when I look inward from the outside is lots and lots of
packet drops and broken connections. Yesterday was bad too, but today is
really terrible. It doesn't appear to be a server thing; the server is
purring along moderatly as usual.
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?
Whatever it is, it's something that's not affecting some people but not
everyone, since there is plenty of activity going on (according to the
various logs).
I wonder if an internal or external line to/from Pair broke or is acting
flaky? IIRC, something semi-similar to this happened about a year ago when
a Cisco router at Pair suffered a hardware failure.
--Todd
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.
|
|
Message has 2 Replies:
 | | Re: Sluggish nntp performance
|
| (...) If you have mtr, run it to some systems out there (like yahoo.com or gerf.org) Here is what it looks like from gerf.org: HOST LOSS RCVD SENT BEST AVG WORST grf-e0.bitwisesystems.com 0% 15 15 0 0 1 ethernet1-0.a1.pia.il.verio.net 0% 15 15 1 3 (...) (25 years ago, 8-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 (...) (25 years ago, 10-Oct-99, to lugnet.admin.general)
|
Message is in Reply To:
| | Sluggish nntp performance
|
| Has anyone seen slow performance from LUGNET's nntp server? The http server is very fast and nimble, etc. but whenever I connect via nntp, it's always slow and sometimes dropping the connection, whether I use port 119, 8000, or 8080. Cheers, - (...) (25 years ago, 8-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
|
|
|
|
