From: Tino Keitel <tino.keitel@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Very slow header cache in mutt if the maildir is on ext3
Date: Wed, 17 Dec 2008 02:03:34 +0100 [thread overview]
Message-ID: <20081217010334.GA1212@dose.home.local> (raw)
In-Reply-To: <20081217005210.GA889@dose.home.local>
On Wed, Dec 17, 2008 at 01:52:10 +0100, Tino Keitel wrote:
[...]
> OK, after glancing at the strace output again, I see that the seek
> offsets are much more linear in the XFS case, whereas they are pretty
> random in the ext3 case. I guess that this is connected to the order
> of the files in the maildir, which depends on the FS type. So this is
> a bug in mutt which makes reading the header cache dead slow if the
> files are in an inconvenient order.
Just for the records: I tested again on ext3 with dir_index disabled,
and the cache was read as quickly as with XFS.
Regards,
Tino
next prev parent reply other threads:[~2008-12-17 1:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 0:16 Very slow header cache in mutt if the maildir is on ext3 Tino Keitel
2008-12-17 0:52 ` Tino Keitel
2008-12-17 1:03 ` Tino Keitel [this message]
2008-12-17 3:25 ` Theodore Tso
2008-12-17 9:10 ` Tino Keitel
2008-12-17 12:32 ` Theodore Tso
2008-12-17 16:17 ` Tino Keitel
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=20081217010334.GA1212@dose.home.local \
--to=tino.keitel@gmx.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.