From owner-freebsd-stable@FreeBSD.ORG Mon Mar 31 06:36:05 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FD6137B404 for ; Mon, 31 Mar 2003 06:36:05 -0800 (PST) Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [192.80.55.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id C537B43F93 for ; Mon, 31 Mar 2003 06:36:03 -0800 (PST) (envelope-from jandrese@mitre.org) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.12.8/8.12.8) with ESMTP id h2VEa2OC027262; Mon, 31 Mar 2003 09:36:02 -0500 (EST) Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31]) by smtpsrv2.mitre.org (8.12.8/8.12.8) with ESMTP id h2VEa0k2018741; Mon, 31 Mar 2003 09:36:00 -0500 (EST) Received: from mm112324-2k.mitre.org (128.29.3.65) by mailhub1.mitre.org with SMTP id 1722415; Mon, 31 Mar 2003 09:35:54 -0500 Message-ID: <3E88524A.1060600@mitre.org> Date: Mon, 31 Mar 2003 09:35:54 -0500 From: Jason Andresen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mattias Pantzare References: <20030330125138.K23911@leelou.in.tern> <3E870CC7.5000204@mac.com> <20030330175605.E23911@leelou.in.tern> <3E87204C.5060304@ludd.luth.se> In-Reply-To: <3E87204C.5060304@ludd.luth.se> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org cc: Lukas Ertl Subject: Re: vinum performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 14:36:06 -0000 Mattias Pantzare wrote: > Lukas Ertl wrote: > >> Ok. But I still don't understand why RAID 5 write performance is _so_ >> bad. >> The CPU is not the bottle neck, it's rather bored. And I don't understand >> why RAID 0 doesn't give a big boost at all. Is the ahc driver known to be >> slow? > > > To do a RAID 5 write you do this: > 1. Read the old data on the blocks that you will write to. > 2. Read the coresponding parity data. > 3. Write the new data. > 4. Write the new parity. Hmm, how about the case where you're writing new data? You shouldn't have to do steps 1 & 2, and yet the RAID5 write performance is still abysmial. I get 4565 K/sec on modern ATA/133 HDDs. Reading is much better at 91908 K/sec at least. -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755