From owner-freebsd-hackers Sat Jul 13 14:10:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA12989 for hackers-outgoing; Sat, 13 Jul 1996 14:10:25 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA12976 for ; Sat, 13 Jul 1996 14:10:22 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id QAA00481; Sat, 13 Jul 1996 16:08:45 -0500 From: Joe Greco Message-Id: <199607132108.QAA00481@brasil.moneng.mei.com> Subject: Re: using ccd for striping? To: michaelv@HeadCandy.com (Michael L. VanLoon -- HeadCandy.com) Date: Sat, 13 Jul 1996 16:08:45 -0500 (CDT) Cc: pst@shockwave.com, hackers@freebsd.org In-Reply-To: <199607132058.NAA06514@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at Jul 13, 96 01:58:43 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > >> Is anyone using the ccd driver in striping mode? I'd like to hear about > >> other people's good/bad experiences before trying it out myself. > > > >I've seen it act a little funny with way large stripe sizes (65536), several > >different times I have seen it develop "non-writable" and "non-accessible" > >zones near the very end of the disk. > > I presume you're talking about the interleave factor? Since you say > large, and 65536, I assume you're saying 64MB stripes? (64K disk > blocks, 32K bytes, wouldn't be "large".) > > Is there a good reason for doing that? I would think you'd get a much > better performance boost by going with interleaved stripes somewhere > between the size of a filesystem cluster to a unit the size of the > smallest drive's cache. (When I say "cluster", I am referring to the > size of a filesystem block -- 8 fragments -- not a disk block -- 512 > bytes.) [...] > Still, I can't think of any reason you'd ever want 64MB interleaved > stripes. I don't see any benefit in such an arrangement. Think about the case where you are not optimizing for bandwidth, but for transactions per second. Think "news spool" :-) Now think about the size of a cylinder group. ;-) Not all problems get solved the same way. I'd rather have a disk with no improvement in bandwidth but a definite improvement in terms of how fast an average random access is. If you have two heads, and 'zones' on the disk.. ... JG