Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 31 Oct 2002 17:00:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 31 Oct 2002 17:00:09 -0500 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:21777 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id ; Thu, 31 Oct 2002 17:00:03 -0500 Message-ID: <3DC1A925.1000703@pobox.com> Date: Thu, 31 Oct 2002 17:05:25 -0500 From: Jeff Garzik User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hans Reiser CC: David Lang , "David C. Hansen" , "Robert L. Harris" , Linux-Kernel Subject: Re: Reiser vs EXT3 References: <3DC1A5D5.8000901@namesys.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1009 Lines: 28 Hans Reiser wrote: > If you want to talk about 2.6 then you should talk about reiser4 not > reiserfs v3, and reiser4 is 7.6 times the write performance of ext3 > for 30 copies of the linux kernel source code using modern IDE drives > and modern processors on a dual-CPU box, so I don't think any amount > of improved scalability will make ext3 competitive with reiser4 for > performance usages. What is the read performance like? write performance isn't the end-all be-all of useful benchmarks, because most servers do far more reading in a day than they will ever write. And like Andrew has pointed out on more than one occasion, reads are usually synchronous, because applications are typically blocking until each read is satisfied. Jeff - 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/