Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262289AbUCBWvG (ORCPT ); Tue, 2 Mar 2004 17:51:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262295AbUCBWtF (ORCPT ); Tue, 2 Mar 2004 17:49:05 -0500 Received: from khan.acc.umu.se ([130.239.18.139]:20096 "EHLO khan.acc.umu.se") by vger.kernel.org with ESMTP id S262289AbUCBWsB (ORCPT ); Tue, 2 Mar 2004 17:48:01 -0500 Date: Tue, 2 Mar 2004 23:47:58 +0100 From: David Weinehall To: Dax Kelson Cc: Peter Nelson , Hans Reiser , linux-kernel , ext2-devel@lists.sourceforge.net, ext3-users@redhat.com, jfs-discussion@oss.software.ibm.com, reiserfs-list@namesys.com, linux-xfs@oss.sgi.com Subject: Re: Desktop Filesystem Benchmarks in 2.6.3 Message-ID: <20040302224758.GK19111@khan.acc.umu.se> Mail-Followup-To: Dax Kelson , Peter Nelson , Hans Reiser , linux-kernel , ext2-devel@lists.sourceforge.net, ext3-users@redhat.com, jfs-discussion@oss.software.ibm.com, reiserfs-list@namesys.com, linux-xfs@oss.sgi.com References: <4044119D.6050502@andrew.cmu.edu> <4044366B.3000405@namesys.com> <4044B787.7080301@andrew.cmu.edu> <1078266793.8582.24.camel@mentor.gurulabs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1078266793.8582.24.camel@mentor.gurulabs.com> User-Agent: Mutt/1.4.1i X-Accept-Language: Swedish, English X-GPG-Fingerprint: 7ACE 0FB0 7A74 F994 9B36 E1D1 D14E 8526 DC47 CA16 X-GPG-Key: http://www.acc.umu.se/~tao/files/pubkey_dc47ca16.gpg.asc Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2001 Lines: 46 On Tue, Mar 02, 2004 at 03:33:13PM -0700, Dax Kelson wrote: > On Tue, 2004-03-02 at 09:34, Peter Nelson wrote: > > Hans Reiser wrote: > > > > I'm confused as to why performing a benchmark out of cache as opposed to > > on disk would hurt performance? > > My understanding (which could be completely wrong) is that reieserfs v3 > and v4 are algorithmically more complex than ext2 or ext3. Reiserfs > spends more CPU time to make the eventual ondisk operations more > efficient/faster. > > When operating purely or mostly out of ram, the higher CPU utilization > of reiserfs hurts performance compared to ext2 and ext3. > > When your system I/O utilization exceeds cache size and your disks > starting getting busy, the CPU time previously invested by reiserfs pays > big dividends and provides large performance gains versus more > simplistic filesystems. > > In other words, the CPU penalty paid by reiserfs v3/v4 is more than made > up for by the resultant more efficient disk operations. Reiserfs trades > CPU for disk performance. > > In a nutshell, if you have more memory than you know what do to with, > stick with ext3. If you spend all your time waiting for disk operations > to complete, go with reiserfs. Or rather, if you have more memory than you know what to do with, use ext3. If you have more CPU power than you know what to do with, use ReiserFS[34]. On slower machines, I generally prefer a little slower I/O rather than having the entire system sluggish because of higher CPU-usage. Regards: David Weinehall -- /) David Weinehall /) Northern lights wander (\ // Maintainer of the v2.0 kernel // Dance across the winter sky // \) http://www.acc.umu.se/~tao/ (/ Full colour fire (/ - 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/