Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: switch to another window while gnus is busy, nnmaildir slow startup
Date: Fri, 12 Dec 2008 15:35:32 -0600	[thread overview]
Message-ID: <86wse5qdp7.fsf@lifelogs.com> (raw)
In-Reply-To: <x8tej0dj0y6.fsf@tool.montefiore.ulg.ac.be>

On Fri, 12 Dec 2008 08:40:33 +0100 Justus-bulk@Piater.name wrote: 
(actually from February 3)
>> The nnmaildir backend starts up slowly (about three minutes for me,
>> with about 25000 messages), apparently because it reads *all* NOV
>> information at startup time.
>> 
>> This approach obviously does not scale well.
>> 
>> My question is: Could this be done on a per-group basis? In this case,
>> the NOV parsing could be deferred to the first time one enters a
>> group, and nnmaildir initial startup should be almost instantaneous.

Yes, but implementing it is not easy because so much of Gnus assumes all
the data is in place.  You could, instead, lower the subscription level
for the nnmaildirs to 5 so they don't get checked on startup, and check
them manually with `M-g'.  I realize it's not a good solution but it's
immediately usable.

Ted




      reply	other threads:[~2008-12-12 21:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 16:56 switch to another window while gnus is busy jidanni
2008-12-11 17:02 ` David Engster
2008-12-11 18:00 ` Tassilo Horn
2008-12-11 18:20 ` Ted Zlatanov
2008-12-12  1:34   ` nnrss slow [was: switch to another window while gnus is busy] jidanni
2008-12-12 21:45     ` nnrss slow Ted Zlatanov
2008-12-13  9:44       ` Steinar Bang
2008-12-15  4:20         ` jidanni
2008-12-16 17:32           ` Ted Zlatanov
2008-12-16 17:35         ` Ted Zlatanov
2008-12-15  4:06       ` jidanni
2008-12-12  7:40   ` switch to another window while gnus is busy, nnmaildir slow startup Justus-bulk
2008-12-12 21:35     ` Ted Zlatanov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86wse5qdp7.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).