Subject:
|
Re: slow server startup
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Wed, 17 Apr 2002 11:40:16 GMT
|
Viewed:
|
186 times
|
| |
|
|
"Chris Gray" <cg@ami-cg.GraySage.COM> wrote in message
news:m3y9fnktjv.fsf@ami-cg.GraySage.COM...
>
> I've noticed this for 2 or 3 weeks now, but haven't commented. When I
> crank up my newsreader (gnus inside Gnu emacs) to read via NNTP from
> lugnet, there is a 1 - 2 minute delay before the newsgroup list starts.
> I don't see that when reading from a couple of other news servers that
> I use. I'm wondering: is lugnet no longer running an NNTP server all
> the time, and has to start one up when a connection is requested? This
> symptom is new as of 2 - 3 weeks ago. Anyone else seeing it?
No problem here. OE6 on W2K Pro on a 2Mbps line in the UK. Also fine from
home on WinME with OE6 on ADSL. Usually connects within 5 seconds or so, and
I'm reading new messages within 30 secs. I can only guess that there is a
delay somewhere between you and the Lugnet news server. Here's a traceroute
I just tried:
TraceRoute - Wednesday, April 17, 2002 12:36:09
Generated by CyberKit Version 2.5
Copyright © 1996-2000 by Luc Neijens
Address: news.lugnet.com
Number of Packets: 1
Packet size: 64
Trace Hop 1 through 30
Timeout: 5
Resolve Addresses: Yes
Don't Fragment: No
#1 Unavailable (212.135.149.1): TTL Exceeded, ttl=255, 20 ms
#2 access0.birmingham.router.easynet.net (212.134.11.227): TTL Exceeded,
ttl=254, 0 ms
#3 access1.thlon.router.easynet.net (212.134.11.41): TTL Exceeded, ttl=253,
10 ms
#4 ge1-0-0.core1.thlon.router.easynet.net (195.40.0.142): TTL Exceeded,
ttl=252, 10 ms
#5 fa2-0-0.bbcore1.thlon.router.easynet.net (207.162.198.2): TTL Exceeded,
ttl=251, 50 ms
#6 p600.atm0-0-0.bbcore0.60hud.router.easynet.net (207.162.207.113): TTL
Exceeded, ttl=250, 81 ms
#7 bar10-serial5-1-0-0.NewYork.cw.net (208.173.133.153): TTL Exceeded,
ttl=249, 100 ms
#8 agr2-loopback.NewYork.cw.net (206.24.194.102): TTL Exceeded, ttl=248, 110
ms
#9 dcr1-so-6-1-0.NewYork.cw.net (206.24.207.53): TTL Exceeded, ttl=246, 110
ms
#10 agr3-so-0-0-0.NewYork.cw.net (206.24.207.58): TTL Exceeded, ttl=245, 90
ms
#11 acr2-loopback.Cleveland.cw.net (208.172.210.62): TTL Exceeded, ttl=245,
120 ms
#12 bar2-loopback.Cleveland.cw.net (208.172.210.4): TTL Exceeded, ttl=244,
100 ms
#13 pair-networks-inc.Cleveland.cw.net (208.172.217.158): TTL Exceeded,
ttl=242, 120 ms
#14 news.lugnet.com (209.197.110.217): Echo Reply, ttl=241, 110 ms
Statistics: Out 14, in 14, loss 0%, times (min/avg/max) 10/73/120 ms
As you can see the response time is only 110ms, so there isn't a routing
issue between my work PC and the server. If you have a much higher value for
the news.lugnet.com entry then that might explain something, or if you have
some packet loss that indicates a hardware problem somewhere along the line
(eg. bottleneck router which is losing packets).
Then again it could be a problem at the server if it's only occurring at
certain times. Being in the UK I obviously access the server mostly during
the US night or early hours, so traffic is probably much lower than during
the US daylight hours. Maybe the server gets overloaded at busy times, or
maybe there's a process running on the server (eg. creating indexes of posts
for the Lugnet search engine) that is eating up CPU cycles and slowing
everything else down. Only the admins will be able to determine if this is
occurring.
Dan
|
|
Message is in Reply To:
 | | slow server startup
|
| I've noticed this for 2 or 3 weeks now, but haven't commented. When I crank up my newsreader (gnus inside Gnu emacs) to read via NNTP from lugnet, there is a 1 - 2 minute delay before the newsgroup list starts. I don't see that when reading from a (...) (22 years ago, 17-Apr-02, to lugnet.admin.general)
|
18 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
