From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/3621 Path: news.gmane.org!not-for-mail From: Nuutti Kotivuori Newsgroups: gmane.emacs.gnus.user Subject: Re: nnimap slow on big groups Date: Mon, 15 Mar 2004 11:49:38 +0200 Organization: Ye 'Ol Disorganized NNTPCache groupie Message-ID: <87brmyv3rh.fsf@aka.i.naked.iki.fi> References: <87n06r9epg.fsf@aka.i.naked.iki.fi> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138669673 19619 80.91.229.2 (31 Jan 2006 01:07:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:07:53 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:32:30 2006 Original-Path: quimby.gnus.org!newsfeed1.e.nsc.no!nsc.no!nextra.com!news01.chello.no!amsnews01.chello.com!newsfeeder.wxs.nl!newsfeed.wxs.nl!newsfeed.stueberl.de!peer1.news.newnet.co.uk!peer1.news.newnet.co.uk!feeder2.news.jippii.net!reader1.news.jippii.net!53ab2750!not-for-mail Original-Newsgroups: gnu.emacs.gnus User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:Y1Z1xQqic/ns0I16BLElxjPPUHQ= Cache-Post-Path: aka.i.naked.iki.fi!unknown@aka.i.naked.iki.fi X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) Original-NNTP-Posting-Host: 62.142.249.112 Original-X-Complaints-To: newsmaster@saunalahti.com Original-X-Trace: reader1.news.jippii.net 1079344180 62.142.249.112 (Mon, 15 Mar 2004 11:49:40 EET) Original-NNTP-Posting-Date: Mon, 15 Mar 2004 11:49:40 EET X-Received-Date: Mon, 15 Mar 2004 10:50:24 MET (news01.chello.no) Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:3762 Original-Lines: 28 X-Gnus-Article-Number: 3762 Tue Jan 17 17:32:30 2006 Xref: news.gmane.org gmane.emacs.gnus.user:3621 Archived-At: Kevin Greiner wrote: > Nuutti Kotivuori writes: >> 'nnimap' seems to be rather slow when selecting a large group - in >> this case, around 65000 messages. >> >> A trivial poking around from me showed that it requests the entire >> SEEN list from the group upon entry, while showing the "Updating >> info for ..." message. Probably there are other operations that are >> happening as well. >> >> Is there anything that can be done to alleviate the problem? > > 1) Agentize the server so that the 65K headers can be cached locally. > 2) Set the agent-predicate to false so that the articles will not be > stored locally. I will try this later on when I get around to it, but I am pretty sure it will not solve my problem. The problem is not that 65k headers would have to be sent over the network. I wouldn't even want to have them locally if I can avoid it. The problem is that nnimap checks if the read article ranges correspond to the 'seen' list on the server, and so fetches only the article numbers of 65k seen articles - but even that is excessive. -- Naked