From: Russ Allbery <rra@stanford.edu>
Subject: Re: Gnus slow incorporating vast quantities of mail
Date: Mon, 14 Jan 2002 10:47:03 -0800 [thread overview]
Message-ID: <yln0zgvkgo.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <y68lmf0vr5b.fsf@nerd-xing.mit.edu> (David Z Maze's message of "Mon, 14 Jan 2002 11:22:40 -0500")
David Z Maze <dmaze@MIT.EDU> writes:
> 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?
Did a lot of that mail sort into the same directory? I don't trust AFS
file creation speed, and I particularly don't trust AFS with large
directories.
Note also that AFS performance can vary a *lot* depending on network
conditions, file server load, and a lot of other things that are hard to
measure or control.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2002-01-14 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 16:22 David Z Maze
2002-01-14 18:47 ` Russ Allbery [this message]
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=yln0zgvkgo.fsf@windlord.stanford.edu \
--to=rra@stanford.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).