From owner-freebsd-fs@FreeBSD.ORG Mon Jun 22 08:14:57 2015 Return-Path: Delivered-To: freebsd-fs@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7771187D for ; Mon, 22 Jun 2015 08:14:57 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5839C1148 for ; Mon, 22 Jun 2015 08:14:57 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) by douhisi.pair.com (Postfix) with ESMTPSA id 47A2C3F6CF for ; Mon, 22 Jun 2015 04:14:56 -0400 (EDT) Message-ID: <5587C3FF.9070407@sneakertech.com> Date: Mon, 22 Jun 2015 04:14:55 -0400 From: Quartz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: FreeBSD FS Subject: ZFS raid write performance? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 08:14:57 -0000 What's sequential write performance like these days for ZFS raidzX? Someone suggested to me that I set up a single not-raid disk to act as a fast 'landing pad' for receiving files, then move them to the pool later in the background. Is that actually necessary? (Assume generic sata drives, 250mb-4gb sized files, and transfers are across a LAN using single unbonded GigE).