Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org
Subject: Re: overview file access when spooling and nnml/nnimap performance
Date: 22 Sep 1999 18:52:01 +0200	[thread overview]
Message-ID: <iluaeqeopn2.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: Hannu Koivisto's message of "22 Sep 1999 18:32:33 +0300"

Hannu Koivisto <azure@iki.fi> writes:

> Thanks, I'll check those out.  I hope that splitting doesn't
> require anything special and could be done with procmail instead of
> that Sieve thingy.  I'd rather avoid converting my 9k .procmailrc
> into another system.

There's a web page describing how to use procmail with Cyrus, so it
can be done even though it's not the intended solution.

> | slow.  Recently, I moved all articles from one 3500 message nnml group
> | to an 8000 message group, and that was real slow.  Towards the end,
> 
> yeah, and when you have 80000 articles instead of 8000, the real
> fun begins :)

Auch. You might be running into filesystem scalability issues then. I
can't tell if it would be a solution for you, but I use something
along the lines of

       (list (format-time-string "INBOX.private.%Y-%m")   ....

for all mailboxes that gather lots of mail which aren't expired. I
began doing this when I used nnml, but, as you can see, kept the
configuration with nnimap.


  parent reply	other threads:[~1999-09-22 16:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-22 13:48 Hannu Koivisto
1999-09-22 14:13 ` Kai Großjohann
1999-09-22 15:32   ` Hannu Koivisto
1999-09-22 15:50     ` Kai Großjohann
1999-09-22 17:00       ` Simon Josefsson
1999-09-22 16:52     ` Simon Josefsson [this message]
1999-09-22 14:54 ` Simon Josefsson
1999-09-22 15:58   ` Hannu Koivisto
1999-09-22 16:17     ` Kai Großjohann
1999-09-22 17:08     ` Simon Josefsson
1999-09-22 18:15       ` Hannu Koivisto
1999-10-04 10:27 ` Robert Bihlmeyer

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=iluaeqeopn2.fsf@badis.pdc.kth.se \
    --to=jas@pdc.kth.se \
    --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).