From: David Z Maze <dmaze@MIT.EDU>
Subject: Gnus slow incorporating vast quantities of mail
Date: Mon, 14 Jan 2002 11:22:40 -0500 [thread overview]
Message-ID: <y68lmf0vr5b.fsf@nerd-xing.mit.edu> (raw)
I was travelling on business for a few days last week, and so my
incoming mail spool got sort of big. (Being on debian-* lists will do
that, somehow... :-) Looking at the Incoming... file:
{15} Mail% grep -c ^L Incoming-4FNdp
2475
{16} Mail% ls -l Incoming-4FNdp
-rw------- 1 dmaze mit 8785983 Jan 12 14:07 Incoming-4FNdp
Gnus seems to have pulled the mail in just fine, but AFAICT sorting it
into folders was really slow; I didn't get to the group buffer for
about half an hour. (Hardware is a Sun Fire 280R, two 750 MHz
UltraSPARC-IIIs, 2.0 GB of RAM, I think I was the only serious user of
the machine at the time; CPU load wasn't an issue, but network latency
of getting to the mail store over AFS probably was.) My suspicion is
that nnmail-split-fancy can be O(n^2) in the size of the incoming mail
spool, meaning that you'll get acceptable performance unless you're
trying to slurp in a truly vast quantity of mail (as I did here).
More configuration details: using nnml (into an AFS directory) fed by
a (Kerberized) POP server, sorting using a moderately complex
nnmail-split-fancy rule set. Most of the time it works reasonably;
'ls -lSr ~/Mail' says that the new three largest Incoming... files I
have are 2.5, 1.4, and 1.2 MB, respectively, and I haven't noticed
sorting those being too painful.
Any hints as to what might cause this? Is this an issue in Gnus, or
my splitting rules, or something else? Is there any easy way to debug
it without letting my mail back up for a week? :-) TIA...
--
David Maze dmaze@mit.edu http://www.mit.edu/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
next reply other threads:[~2002-01-14 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 16:22 David Z Maze [this message]
2002-01-14 18:47 ` Russ Allbery
2002-01-14 19:19 ` David Z Maze
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=y68lmf0vr5b.fsf@nerd-xing.mit.edu \
--to=dmaze@mit.edu \
/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).