From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 05:32:36 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FE8F16A4CE for ; Wed, 12 May 2004 05:32:36 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E694F43D54 for ; Wed, 12 May 2004 05:32:35 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (g4.samsco.home [192.168.0.12]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4CCbSu6066840; Wed, 12 May 2004 06:37:28 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A2192B.3010201@freebsd.org> Date: Wed, 12 May 2004 06:31:39 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040214 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pete French References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 12:32:36 -0000 Pete French wrote: >>Read caching should be turned off unless you have a very specific need >>for it. Having it on is going to hurt sequential read performance by a >>2x factor. The only time is makes sense is when you have a relatively >>small data set that gets read repeatedly, with few other reads mixed in. > > > Interesting comment. Does that refer to this particular controller, to > caches on RAID controllers in general, or to caches on the drives themselves ? > > -pete. With the read cache on, every time that the OS requests a new logical block that isn't in the cache, the controller has to first DMA that block from the disks into the cache, then DMA from the cache to host memory. With the read cache off, it only has to DMA from the disks straight to host memory. Some older AAC controllers also don't balance the cache well between read and write, so having both enabled winds up thrashing both. The read cache on the drive is a good thing since it will do a bit of read-ahead which will help reduce latency. Scott