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. AFAIK, SM2.0 check for new newsgroup messages in several cases: • at startup, if the "Check for new messages at startup" setting is checked for the relevant newserver; • every x minutes, if the "Check for new messages every x minutes" is checked for the relevant newserver; • when the newserver is expanded in the Folder Pane, if the about:config -> news.update_unread_on_expand setting is true (that's the default in SM2.0); • when the user click on a newsgroup in the Folder Pane (I don't know if this is always true, or only if about:config -> news.update_unread_on_expand is false). That said, the point is that SM2.0 is considerably slower and consumes a very bigger amount of CPU time than SM1.1.18 to perform this task. Moreover, if the CPU isn't powerful enough, SM becomes unresponsive for a varying amount of seconds until the check is done. I think this is the very same issue that was causing the application stalls and CPU burst discussed in this thread: <http://groups.google.com/group/mozilla.support.seamonkey/browse_thread/thread/b2ca52cd58029e13/> I haven't tried to reproduce this issue with a fresh new profile, yet, but I think I experienced it after the profile migration from SM1.1.18 to SM2.0: with the "Check for new messages every x minutes" setting checked (just like it was on SM1.1.18), SM2.0 was unusable for the frequent stalls. We absolutely need a bug report about this. I'm not a very good English writer, but if there are no other voluntaries I'll file it after testing with a new profile and drop here the bug number. -- Andrea "XFox" Govoni AIM/iChat/ICQ: [email protected] Yahoo! ID: xfox82 Skype Name: draykan PGP KeyID: 0x212E69C1 Fingerprint: FBE1 CA7D 34BE 4A53 9639 5C36 B7A0 605F 212E 69C1 _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
