From owner-freebsd-fs@FreeBSD.ORG Thu Nov 13 07:30:30 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E15F106567C; Thu, 13 Nov 2008 07:30:30 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-71-182-69-106.ptldor.fios.verizon.net [71.182.69.106]) by mx1.freebsd.org (Postfix) with ESMTP id 63B708FC12; Thu, 13 Nov 2008 07:30:29 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: by sopwith.solgatos.com (Postfix, from userid 66) id F1EDA3F22; Wed, 12 Nov 2008 22:46:48 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id GAA26763; Thu, 13 Nov 2008 06:57:58 GMT Message-Id: <200811130657.GAA26763@sopwith.solgatos.com> To: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org In-reply-to: Your message of "Thu, 13 Nov 2008 15:46:32 +1000." <491BBF38.9010908@dannysplace.net> Date: Wed, 12 Nov 2008 22:57:58 +0000 From: Dieter X-Mailman-Approved-At: Thu, 13 Nov 2008 12:23:50 +0000 Cc: Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 07:30:30 -0000 >> For the array(s) >> 9 x ST31000340AS 1tb disks >> 1 x ST31000333AS 1tb disk (trying to swap this for a ST31000340AS) > There seems to be little difference between enabling and disabling the > disk cache on the Areca. This leads me to two conclusions: > 1. Disabling the write cache does nothing on Seagate drives. > 2. IO to the drives is so slow that a write cache is irrelevant. I have a couple of the ST31000340AS 1TB disks as well as older lower capacity Seagates, and turning the write cache on/off makes a MASSIVE (roughly 10:1) difference in write speed. Jeremy reports "about 13%" with Seagate ST3120026AS: http://lists.freebsd.org/pipermail/freebsd-hardware/2008-October/005450.html Perhaps there is something about the Areca or the testing? Is the write cache really getting turned on/off? You're getting about 2-3x the speed I'd expect if the write cache were off, so maybe it is still on but there is a bottleneck elsewhere? Have you tried a simple test with /dev/zero and dd to a raw drive to eliminate the effects of the filesystem?