From owner-freebsd-geom@FreeBSD.ORG Fri May 4 01:42:40 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7328616A402 for ; Fri, 4 May 2007 01:42:40 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from auriate.fluffles.net (cust.95.160.adsl.cistron.nl [195.64.95.160]) by mx1.freebsd.org (Postfix) with ESMTP id 2A86413C458 for ; Fri, 4 May 2007 01:42:40 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from destiny ([10.0.0.21]) by auriate.fluffles.net with esmtpa (Exim 4.66 (FreeBSD)) (envelope-from ) id 1Hjmod-000Jl7-16; Fri, 04 May 2007 03:42:35 +0200 Message-ID: <463A8F9C.8020205@fluffles.net> Date: Fri, 04 May 2007 03:42:52 +0200 From: Fluffles User-Agent: Thunderbird 1.5.0.8 (X11/20061114) MIME-Version: 1.0 To: "Wilkinson, Alex" References: <1847971490.20070503223307@uzvik.kiev.ua> <971656.83802.qm@web30315.mail.mud.yahoo.com> <593515236.20070504022900@uzvik.kiev.ua> <463A7558.9090600@fluffles.net> <20070504011646.GD15396@obelix.dsto.defence.gov.au> In-Reply-To: <20070504011646.GD15396@obelix.dsto.defence.gov.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org Subject: Re: graid5 compilation problem X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2007 01:42:40 -0000 Wilkinson, Alex wrote: > 0n Fri, May 04, 2007 at 01:50:48AM +0200, Fluffles wrote: > > >deniswork@uzvik.kiev.ua wrote: > >> Thanks, this help! > > Question: Is there a graid5 guide anywhere ? > I would like to test this code out. > I'm working on one; but basically it's compile (works on both 6 and 7-CURR) and go using "graid5 label ". and you can use it straight away. I've done extensive benchmarking but results depend on: - hardware, especially CPU/MEM/BUS technology - disk bus bandwidth; avoid PCI whenever possible, PCI is depricated. Use onboard connectors directly tied to chipset if possible - the version of graid5, stable or TNG (take the graid5-eff.tbz package instead of graid5.tbz); TNG has nice speed improvements - disk speeds themselves Under the right conditions (dualcore with 8 SATA disks on embedded bus) it is possible to achieve 400MB/s *write* throughput, which is short of amazing considering this is 100% software RAID, and leaves many XOR-hardware RAID solutions behind. ;-) - Veronica