From owner-freebsd-hardware@FreeBSD.ORG Tue Aug 28 23:47:10 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0546A1065670 for ; Tue, 28 Aug 2012 23:47:10 +0000 (UTC) (envelope-from ayoung@mosaicarchive.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id A37C08FC15 for ; Tue, 28 Aug 2012 23:47:09 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so8408310vcb.13 for ; Tue, 28 Aug 2012 16:47:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to :x-gm-message-state; bh=NDgxLgR8uChIulEWymWj0SOtqaSjQRvn3jyRdzom49A=; b=PHI/00CDvKUPqK2w1Tzgz19ncagNZoutfUIv1MWMkHmjeUf8S6/F+VJhSnfN8G07AP dQz1JjP/itsT11Lvdhlt0vyXh+PeKgf8HsVF6WePRnPscOUsePPBU6hko5vRqYwT57x6 SNnGhZUJ33y2QBPMv2Xol1jDvALdcfBCtVCq9WlGcy99m8TKnIdeP1ZwTjh8I/KF+/f/ sGWMQaFcurg65qAWIiULYHvsQmF6DTN+YghiTtDW9Ti5lJcER0MIEWlVheNb98OrM8CW NEa7cDrMdDoJHKrm6FEoDumv/oW89vf1OgRNYVgV+zj5jXhW0Ajvrxp3Y/TZJ6HRwtHZ 0z/w== Received: by 10.52.98.67 with SMTP id eg3mr13621020vdb.5.1346197628845; Tue, 28 Aug 2012 16:47:08 -0700 (PDT) Received: from [192.168.1.3] (pool-96-237-242-243.bstnma.fios.verizon.net. [96.237.242.243]) by mx.google.com with ESMTPS id by3sm12084047vdc.17.2012.08.28.16.47.07 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 28 Aug 2012 16:47:08 -0700 (PDT) References: <503D3026.6010901@ixsystems.com> <503D4F48.9020108@tcbug.org> In-Reply-To: <503D4F48.9020108@tcbug.org> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: <3F6C1EB2-1EC4-4863-A5BF-093649D9D61C@mosaicarchive.com> X-Mailer: iPhone Mail (9B206) From: Andrew Young Date: Tue, 28 Aug 2012 19:47:05 -0400 To: Josh Paetzel X-Gm-Message-State: ALoCoQkvXU/VR7rVJkYfGFQi2d7Z3G0VDWGiM5S1kXLnEtvaAjSOg1pP5POYhX2ofOOO5vKtIG/C Cc: "freebsd-hardware@freebsd.org" Subject: Re: Support for Fusion IO drives? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2012 23:47:10 -0000 Thanks for the great feedback Josh! The optimum size for an ssd zil device w= as still an open question for us. I'm really glad to hear that they don't ne= ed to be that big. What does zfs do with the zil if there is no dedicated zil device? Our serve= rs consist of a small sata drive that holds the OS and a boatload of larger d= rives on a sas bus. What I'm wondering is if I simply replace the OS disk wi= th an ssd will I get the same performance boost as if I added a dedicated ss= d zil?=20 Thanks! Andy On Aug 28, 2012, at 7:07 PM, Josh Paetzel wrote: >>> -------- Original Message -------- >>> Subject: Support for Fusion IO drives? >>> Date: Tue, 28 Aug 2012 16:46:00 -0400 >>> From: Andy Young >>> To: freebsd-hardware@freebsd.org >>>=20 >>>=20 >>> We are investigating adding SSDs as ZIL devices to boost our ZFS write >>> performance. I read an article a while ago about iX Systems teaming up >>> with >>> Fusion IO to integrate their hardware with FreeBSD. Does anyone know >>> anything about supported drivers for Fusion IO's iodrives? >>>=20 >>> Thanks! >>>=20 >>> Andy >>> _______________________________________________ >>> freebsd-hardware@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >>> To unsubscribe, send any mail to >>> "freebsd-hardware-unsubscribe@freebsd.org" >>>=20 >>>=20 >>>=20 >>>=20 >=20 > I'll put on my iXsystems hat here, as well as my fast storage, ZFS and > Fusion-I/O hat. >=20 > The ZFS filesystem supports dedicated ZIL devices, which can accelerate > certain types of write requests, notably related to fsync. The VMWare > NFS client issues a sync with every write, and most databases do as > well. In those types of environments having a fast dedicated ZIL device > is almost essential. In other environments the benefits of a dedicated > ZIL range from non-existent to substantial. >=20 > A good dedicated ZIL device is all about latency. It doesn't need to be > large, in fact it will only ever handle 10 seconds of writes, so 10x > network bandwidth is worst case. (In most environments this means 20GB > is larger than needed). >=20 > Fusion-I/O cards are far too large to be cost effective ZIL devices. > Even though they do rock at I/O latency, the really fast ones are also > fairly large, so the $/GB on them isn't so attractive. There are better > options for ZIL devices. >=20 > Another consideration is the Fusion-I/O driver is fairly memory hungry, > which competes with memory ZFS wants to use for read caching. >=20 > Now as an L2ARC device, that's a whole different can of worms. >=20 > Command line used: iozone -r 4k -s 96g -i 0 -i 1 -i 2 -t 8 > Parent sees throughput for 8 readers =3D 1712399.95 KB/sec > L2 ARC Breakdown: 197.45m > Hit Ratio: 98.61% 194.71m > L2 ARC Size: (Adaptive) 771.13 GiB > ARC Efficiency: 683.40m > Actual Hit Ratio: 71.09% 485.82m >=20 > ~ 800GB test data, all served from cache. >=20 > If you are considering Fusion-I/O, the FreeBSD driver is generally not > released to the general public by Fusion-I/O, but can be obtained from > various partners. (I believe iXsystems is the only FreeBSD friendly > fusion-i/o partner but could be wrong about that) >=20 >=20 > --=20 > Thanks, >=20 > Josh Paetzel >=20