Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 31 Oct 2002 17:57:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 31 Oct 2002 17:57:32 -0500 Received: from sphinx.mythic-beasts.com ([195.82.107.246]:36359 "EHLO sphinx.mythic-beasts.com") by vger.kernel.org with ESMTP id ; Thu, 31 Oct 2002 17:57:31 -0500 Date: Thu, 31 Oct 2002 23:03:43 +0000 (GMT) From: Matthew Kirkwood X-X-Sender: To: Jeff Garzik cc: Hans Reiser , Linux-Kernel Subject: Re: Reiser vs EXT3 In-Reply-To: <3DC1A925.1000703@pobox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1098 Lines: 30 On Thu, 31 Oct 2002, Jeff Garzik wrote: > > reiser4 is 7.6 times the write performance of ext3 > > for 30 copies of the linux kernel source code using modern IDE drives > 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. I'm not sure how true that is these days. OLTP DB servers with a lot of RAM will typically do more write traffic, all pushed by fsync, than reads. (Some may claim that that means your server is overspecced, of course.) Other servers, too, look rather like that -- mail servers do a lot of fsync, web servers generally have smallish web trees but write a lot of logs... Even on data warehousing apps, there will be a fairly high level of writes due to use of temporary relations.. Matthew. - 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/