From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 11:32:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE39D16A4CE for ; Wed, 24 Nov 2004 11:32:29 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2295F43D49 for ; Wed, 24 Nov 2004 11:32:29 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iAOBWNOf017593 for ; Wed, 24 Nov 2004 12:32:23 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <41A47147.7040403@fer.hr> Date: Wed, 24 Nov 2004 12:32:23 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <41A2488F.8030802@fer.hr> <20041122215228.J568@korben.in.tern> <41A33907.5020703@fer.hr> <20041124103613.GL7232@darkness.comp.waw.pl> In-Reply-To: <20041124103613.GL7232@darkness.comp.waw.pl> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: gvinum panic? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 11:32:30 -0000 Pawel Jakub Dawidek wrote: > +> linear read (1024 MB file, blocks of 32768) ................. 38.5 MB/s > +> linear write (1024 MB file, blocks of 32768) ................ 16.8 MB/s > +> random read (1024 MB file, blocks of 32768) ................. 41.9 MB/s > +> random write (1024 MB file, blocks of 32768) ................ 3.4 MB/s > In the interests of archives, I must say that the "random read" score above is WRONG. I was surprised myself because it's RAID3, so I rerun the test. Here are the correct numbers: linear read (2048 MB file, blocks of 32768) ................. 40.3 MB/s linear write (2048 MB file, blocks of 32768) ................ 16.8 MB/s random read (2048 MB file, blocks of 32768) ................. 5.1 MB/s random write (2048 MB file, blocks of 32768) ................ 2.9 MB/s (previously, most of the file has fitted into cache) > Do you use parity component for reading? If no, you can try it (add '-r' > option while configuring your raid3 device), it should speed up random > reads a lot. My situation is that there are 3 discs on 2 IDE channels, so two are in master-slave relationship. I've put the parity drive on the slave disc, and without -r it doesn't ever get touched (which speeds up the requests) The tests confirm this was right: (with round-robin/parity reads:) linear read (2048 MB file, blocks of 32768) ................. 32.6 MB/s linear write (2048 MB file, blocks of 32768) ................ 16.8 MB/s random read (2048 MB file, blocks of 32768) ................. 4.0 MB/s random write (2048 MB file, blocks of 32768) ................ 3.1 MB/s