From owner-freebsd-current Sun Oct 6 23:42:12 2002 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 5FB2337B401; Sun, 6 Oct 2002 23:42:11 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id F02B243E7B; Sun, 6 Oct 2002 23:42:10 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.4) with ESMTP id g976g2PQ045530; Sun, 6 Oct 2002 23:42:02 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.4/Submit) id g976g1nO045529; Sun, 6 Oct 2002 23:42:01 -0700 (PDT) (envelope-from dillon) Date: Sun, 6 Oct 2002 23:42:01 -0700 (PDT) From: Matthew Dillon Message-Id: <200210070642.g976g1nO045529@apollo.backplane.com> To: "Greg 'groggy' Lehey" Cc: Vallo Kallaste , Lars Eggert , Poul-Henning Kamp , n0go013 , current Subject: Re: ccd performance (was: [ GEOM tests ] vinum drives lost) References: <62515.1033758160@critter.freebsd.dk> <3D9DEFF7.7050508@isi.edu> <20021005125505.GA1248@tiiu.internal> <20021005221456.GR83766@wantadilla.lemis.com> <20021006072155.GA1117@tiiu.internal> <200210061830.g96IUGNF043142@apollo.backplane.com> <20021007014255.GC93490@wantadilla.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> a lot of information on how to use it. I generally recommend :> using a stripe size of 1152 for multitasking loads. : :Sectors? Why particularly this value? It's described in 'tuning'. Basically you want a fairly large stripe to reduce multi-disk seeking when reading sequential files (that is, if you do not need the combined bandwidth of more then one drive for the sequential case), and you also want to use a stripe that does not cause meta-data (e.g. inodes and bitmaps) to wind up on just one drive, e.g. use 1152 instead of 1024. or you will wind up with unbalanced accesses. :ccd, but I know a lot of cheap hardware RAID arrays always read an :entire stripe at a time, which requires more memory and takes longer. :Have you checked ccd for this? : :Greg I've done extensive work on ccd. It does not try to read a whole stripe, it just breaks the I/O up as appropriate, issues duel-I/O for mirror writes, and tries to select a reasonable (single) side when doing a read from a mirrored area. I even have a little code in there to try to reduce unnecessary seeking when reading from a mirrored area. But, again, CCD is not trying to implement 'real' RAID. It can't rebuild a lost mirror drive, for example, and does not implement RAID-5. IMHO A real RAID controller with NVRAM should be used for those things. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message