From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: very poor ext3 write performance on big filesystems? Date: Tue, 19 Feb 2008 10:06:50 -0500 Message-ID: <200802191006.50693.chris.mason@oracle.com> References: <47B980AC.2080806@wpkg.org> <20080218141640.GC12568@mit.edu> <47BAED94.3040103@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Cc: Theodore Tso , Andi Kleen , LKML , LKML To: Tomasz Chmielewski Return-path: Received: from rgminet01.oracle.com ([148.87.113.118]:64839 "EHLO rgminet01.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751970AbYBSPID (ORCPT ); Tue, 19 Feb 2008 10:08:03 -0500 In-Reply-To: <47BAED94.3040103@wpkg.org> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tuesday 19 February 2008, Tomasz Chmielewski wrote: > Theodore Tso schrieb: > > (...) > > > The following ld_preload can help in some cases. Mutt has this hack > > encoded in for maildir directories, which helps. > > It doesn't work very reliable for me. > > For some reason, it hangs for me sometimes (doesn't remove any files, rm > -rf just stalls), or segfaults. You can go the low-tech route (assuming your file names don't have spaces in them) find . -printf "%i %p\n" | sort -n | awk '{print $2}' | xargs rm > > > As most of the ideas here in this thread assume (re)creating a new > filesystem from scratch - would perhaps playing with > /proc/sys/vm/dirty_ratio and /proc/sys/vm/dirty_background_ratio help a > bit? Probably not. You're seeking between all the inodes on the box, and probably not bound by the memory used. -chris