Closed Bug 353980 Opened 18 years ago Closed 17 years ago

Newsgroup refresh takes too long

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.8 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: epp, Unassigned)

Details

(Keywords: perf)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060919 SeaMonkey/1.1b
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060919 SeaMonkey/1.1b

I attempted to refresh the newsgroups listing from my ISP (Comcast) using SeaMonkey 1.1Bb.  The entire refresh took 11 (eleven) minutes.  In comparison, Outlook Express took only a little more than 2 (two) minutes to do the same refresh.

Comcast informs me that it should take no more than a couple of minutes to refresh the list on a 6 Mb connection (which I have).

There would appear to be an issue with SM's news reader that is causing a refresh to be extremely sluggish.  




Reproducible: Always

Steps to Reproduce:
1.Launch SeaMonkey News
2.Refresh newsgroups
3.Total refresh is sluggish

Actual Results:  
Refresh took 11 minutes, much too long on a 6 Mb connection.

Expected Results:  
ISP informs me that a refresh should take no longer than a couple of minutes, which is the timeframe it took Outlook Express to do the same thing.

Not an issue with SeaMonkey 1.0.5.
Version: unspecified → 1.8 Branch
SeaMonkey version should read "1.1b".
Also tried this with the Linux release of SM 1.1b (Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.8.1) Gecko/20060916 SeaMonkey/1.1b), it downloaded the list in 2 minutes.

This issue appears to only affect the Windows release.
You mean you refreshed the newsgroups list of the Comcast/Giganews newsserver? Do you have any firewall installed? Do downloads in the browser have normal speed?
Yes, from the Comcast/Giganews newsserver.

A firewall is installed (part of CA eTrust Internet Security Suite), there is also a router present.

Everything else that is browser-related:  e-mail, web browsing, file downloads, ChatZilla, all extremely fast, no problems with any of these.

The only problem is the newsgroup listing refresh is sluggish.  After a second attempt to refresh the listing, which was sluggish both times, I opened this bug report.  OE's refresh occurred between these two and as mentioned above, only took a couple of minutes.

  

Update:

OE 6:               Speed unknown, took 2 minutes for a refresh.

SM 1.0.5 Windows:   Speed 62.6 KB/sec, took  2 minutes for a refresh.
SM 1.1a  Windows:   Speed 11.2 KB/sec, took  6 minutes for a refresh.
SM 1.1b  Windows:   Speed  6.0 KB/sec, took 11 minutes for a refresh.

SM 1.1b  Linux:     Speed 40.0 KB/sec, took  2 minutes for a refresh.

Evidently, something happened between the 1.0.5 and 1.1a Windows releases of SeaMonkey that caused a degrading in performance pertaining to newsgroup refreshes, which obviously became worse in the 1.1b Windows release.

this is just updating the counts for the groups, not downloading the headers for the groups? Or is this going into the subscribe UI and picking refresh? I tried this with a trunk TB build (all the code is the same), and it was very fast...
This is going into the Subscribe UI and selecting Refresh.

The newsgroup account name is highlighted, over on the right, the link titled "Manage newsgroup subscriptions" is selected.  This opens up a small window titled "Subscribe".  The Refresh button is selected inside the Subscribe window.
Just tried the same with the latest trunk of 1.5a for Windows:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060926 SeaMonkey/1.5a

Even worse than 1.1b!  Downloads the first 617 newsgroup names, waits one minute, then downloads the next 604.

Something HAD to have changed between the 1.0.5 and 1.1x releases...




In the latest 1.1 release candidate:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1

this problem is still present.  

In looking at my earlier comments, I forgot to mention that this is via SSL connection to their news server.  Because the server requires our Comcast login to access, they offered an option to connect via SSL as a result of customer requests.

(In reply to comment #7)
> This is going into the Subscribe UI and selecting Refresh...

Edward, an accurate STR is not a description of is what you did, but a complete list of every action you take and thing you see.  So based on your earlier comments, your STR really is 4 items:

1. highlight newsgroup account name
2. click "Manage newsgroup subscriptions" 
3. see Subscribe window
4. click refresh 

do you see this using the current seamonkey trunk, 2.x?

what is the news url, news.Comcast.com ?
Severity: critical → normal
Keywords: perf
I have not tried this with SeaMonkey 2.x under Windows.  I am currently using SM 1.1.4 and still encounter this with the Windows release.  

SM 1.1.4 for Linux does not exhibit this.

Server is newsgroups.comcast.net, one must be a Comcast customer to use it.

Closing bug as a subsequent version of SeaMonkey apparently cleared this problem up.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Component: MailNews: Subscribe → MailNews: Message Display
QA Contact: search
You need to log in before you can comment on or make changes to this bug.