On 11/09/2009 04:56 PM, NoOp wrote: > On 11/09/2009 06:10 AM, Andrea Govoni wrote: >> on 09/11/09 05:08 NoOp said the following: >>> >>> On 11/08/2009 07:10 PM, Kent Briggs wrote: >>>> >>>> Yeah, that's nothing. The delays show up when you got multiple groups >>>> with 50,000 or more posts in them. >>> >>> You may have missed this from my previous post: >>> gmane.linux.ubuntu.user - 200054 (goes back to 2004) >>> That is: >>> 200,054 >>> and is 4 times your 50,000 posts. >>> >>> Scroll up to the top to the group, click & instantaneously get: >>> Newsgroups: gmane.linux.ubuntu.user >>> Subject: Re: D-Link Airplus DWL-G650+ >> >> I think you're misunderstanding Kent's complaint. >> The big delay and high CPU activity that Kent is referring to is when >> newsgroups with many thousands of messages already downloaded are >> checked for new messages. It's not when a message is displayed or when >> SM2.0 downloads the number of headers you want the *first* time that a >> newsgroup is checked. > > I think I do understand his complaint. I just installed a fresh SM 2.0 > on one of my test systems[1] and added news.gmane.org. I then subscribed > to two newsgroups: > > 1. gmane.linux.ubuntu.user > 200394 new message headers... > 2. gmane.linux.emulators.virtualbox.general > 7525 new message headers to download... > > For both groups I can: 1) elect to download 500 headers (default), 2) > change from 500 to some other number, 1000 for instance, or 3) Download > all headers. > > Obviously if I elect to download all headers from either one it will > take me some time to do so. So I pick #1 above and elect to download all > 200,394 headers. > > I start at 4:30 PM PDT & watch as the downlod progresses. news.gmane.org > is cooperating today, so it seems to be going along smoothly... > 4:35 PM and I am at 130501 headers... > 4:37 and I seem to be hanging on header 200013 - that may be an issue > with the server or the msg itself. Nope, just some fool they let post a > pdf. > 4:39 all 200396 (two more were added in the process) are there. I click > on one from 17 Sep 2004 & it loads just fine. > > I then close & restart SeaMonkey 2.0 and access the same > gmane.linux.ubuntu.user immediately after startup. I time it using a > clock display (w/seconds) on the other computer (click on the > newsgroup): takes ~15 seconds. > > I then modify news.update_unread_on_expand and set to false & repeat the > above (including restart). Time to open the newsgroup: ~15 seconds. > > Keep in mind, the specs of the memory of the machine (see [1] below), > I'll load up 1.1.18 and repeat later tonight or tomorrow on the same low > memory machine. > > [1] The test system is a 1.8Ghz/245Mb running Ubuntu linux 9.10 with a > 1.5Mb DSL link. I've made _no_ modifications to SeaMonkey other than > basic setup.
OK. Testing with 1.1.18 on the exact same test machine: Click on gmane.linux.ubuntu.user and elect to download all 200408 headers. I start at 5:49 PM: get a wait cursor & he download starts. Download take about 5 minutes again. Interesing... I note that the _all_ the msg headers appear as *Read* vs *Unread*. So I click 'Next' to see if it finds the next 'Unread' msg in the the group & wait... and wait, and wait. 1.1.18 is stuck with the 'Next' button lit & I have to kill SeaMonkey. Restart 1.1.18 & again open mailnews & click on news.gmane.org & it takes over 3 seconds to just show the newsgroups. Click on gmane.linux.ubuntu.user @ 6:08 PM: headers start appearing instantaneously, but then before selecting any msg I click on 'Date' to sort by date... 1.1.18 freezes again & I have to kill the app to restart & test again. Restart 1.1.18 & again open mailnews & click on news.gmane.org & it takes 5 seconds while checking... gmane.linux.ubuntu.user; again the msg headers appear instantly. This time I just click on the most recent msg; works & appears instantly. Click on 'Date' to sort by date... wait, wait, wait, 5 minutes later & still waiting... in the meantime 1.1.18 has sucked up all of the machines memory (remember it's only a 256MB (previous 245 was incorrect) ram machine. Nope, everythings, frozen & I have to kill 1.1.18 again. Just to be fair, I load up SM 2.0 again & repeat the above 'Date' sort; instantanious sort (both directions - up/down). Try 1.1.18 again, wash, rinse, repeat... SM 1.1.18 hangs. I have to kill the 1.1.18 app to get my memory back (I waited over 5 minutes). Personally, I'd rather take the few added seconds to see the newsgroup appear in SM 2.0 etc., than have to to kill the 1.1.18 app. I suspect the some of you folks know how to do the same to test on your Windows machines. Please do so & then file a bug & I'll be happy to contribute from the linux side. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
