Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756217AbYLQBDr (ORCPT ); Tue, 16 Dec 2008 20:03:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751489AbYLQBDh (ORCPT ); Tue, 16 Dec 2008 20:03:37 -0500 Received: from eazy.amigager.de ([213.239.192.238]:32966 "EHLO eazy.amigager.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751190AbYLQBDg (ORCPT ); Tue, 16 Dec 2008 20:03:36 -0500 Date: Wed, 17 Dec 2008 02:03:34 +0100 From: Tino Keitel To: linux-kernel@vger.kernel.org Subject: Re: Very slow header cache in mutt if the maildir is on ext3 Message-ID: <20081217010334.GA1212@dose.home.local> Mail-Followup-To: linux-kernel@vger.kernel.org References: <20081217001625.GA3250@x61> <20081217005210.GA889@dose.home.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081217005210.GA889@dose.home.local> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/