From owner-freebsd-fs@FreeBSD.ORG Wed May 11 22:38:57 2011 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 71081106564A for ; Wed, 11 May 2011 22:38:57 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2467A8FC14 for ; Wed, 11 May 2011 22:38:57 +0000 (UTC) Received: by iwn33 with SMTP id 33so1288320iwn.13 for ; Wed, 11 May 2011 15:38:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:x-openpgp-key-id:x-openpgp-key-fingerprint :x-openpgp-key-url; bh=XOWoUv0xjw8dEXQmU00hfRE0ZfN/M9+Lje7UDJImJuE=; b=qFoCI9G6fG44/tl8DKXFxtYbxl7tOTY6mfh2l72iSP+EVGJubABGBCreLX5nL9601a H0A0psHO4VFpfkgcBPjeED46CfhziMB4SV4/Dv3nkIsfsE/LFxA8kGCaSep9r164ggCB UorEOa6tTkcu2BuHg1kKiQGSdtVxP7VjHwdQc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-openpgp-key-id :x-openpgp-key-fingerprint:x-openpgp-key-url; b=tZB/DP1UQnjB1A74N800ltnqZ/rxbFDn2p5Is6fv/eGSNUUmhAGM9X4WuGaaiz9uLc hv4TPs85cFM70W5zqznHi+fS6O0UebEV2HzC4ELWnijlzQxrliAhL70xmdbNYxiHNY2a cjc27Y1Urch7BtinFQndWVKJw8nULmsFD4ITg= Received: by 10.42.170.3 with SMTP id d3mr2102112icz.438.1305153536037; Wed, 11 May 2011 15:38:56 -0700 (PDT) Received: from DataIX.net (adsl-99-190-84-116.dsl.klmzmi.sbcglobal.net [99.190.84.116]) by mx.google.com with ESMTPS id d9sm205968ibb.2.2011.05.11.15.38.53 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 May 2011 15:38:54 -0700 (PDT) Sender: "J. Hellenthal" Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.4/8.14.4) with ESMTP id p4BMconB074933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 May 2011 18:38:51 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.4/8.14.4/Submit) id p4BMcnFu074932; Wed, 11 May 2011 18:38:49 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Wed, 11 May 2011 18:38:49 -0400 From: Jason Hellenthal To: Jeremy Chadwick Message-ID: <20110511223849.GA65193@DataIX.net> References: <4DCA5620.1030203@dannysplace.net> <20110511100655.GA35129@icarus.home.lan> <4DCA66CF.7070608@digsys.bg> <20110511105117.GA36571@icarus.home.lan> <4DCA7056.20200@digsys.bg> <20110511120830.GA37515@icarus.home.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: <20110511120830.GA37515@icarus.home.lan> X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E X-OpenPGP-Key-URL: http://bit.ly/0x89D8547E Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: How to enable cache and logs. 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: Wed, 11 May 2011 22:38:57 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Jeremy, On Wed, May 11, 2011 at 05:08:30AM -0700, Jeremy Chadwick wrote: > On Wed, May 11, 2011 at 02:17:42PM +0300, Daniel Kalchev wrote: > > On 11.05.11 13:51, Jeremy Chadwick wrote: > > >Furthermore, TRIM support doesn't exist with ZFS on FreeBSD, so folks > > >should also keep that in mind when putting an SSD into use in this > > >fashion. > > > > By the way, what would be the use of TRIM for SLOG and L2ARC devices? > > I see absolutely no benefit from TRIM for the L2ARC, because it is > > written slowly (on purpose). Any current, or 1-2 generations back SSD > > would handle that write load without TRIM and without any performance > > degradation. > > > > Perhaps TRIM helps with the SLOG. But then, it is wise to use SLC > > SSD for the SLOG, for many reasons. The write regions on the SLC > > NAND should be smaller (my wild guess, current practice may differ) > > and the need for rewriting will be small. If you don't need to > > rewrite already written data, TRIM does not help. Also, as far as I > > understand, most "serious" SSDs (typical for SLC I guess) would have > > twice or more the advertised size and always write to fresh cells, > > scheduling an background erase of the 'overwritten' cell. >=20 > AFAIK, drive manufacturers do not disclose just how much reallocation > space they keep available on an SSD. I'd rather not speculate as to how > much, as I'm certain it varies per vendor. >=20 Lets not forget here: The size of the separate log device may be quite=20 small. A rule of thumb is that you should size the separate log to be able= =20 to handle 10 seconds of your expected synchronous write workload. It would= =20 be rare to need more than 100 MB in a separate log device, but the=20 separate log must be at least 64 MB. http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide So in other words how much is TRIM really even effective give the above ? Even with a high database write load on the disks at full compacity of the= =20 incoming link I would find it hard to believe that anyone could get the=20 ZIL to even come close to 512MB. Given most SSD's come at a size greater than 32GB I hope this comes as a=20 early reminder that the ZIL you are buying that disk for is only going to= =20 be using a small percent of that disk and I hope you justify cost over its= =20 actual use. If you do happen to justify creating a ZIL for your pool then= =20 I hope that you partition it wisely to make use of the rest of the space=20 that is untouched. For all other cases I would reccomend if you still want to have a ZIL that= =20 you take some sort of PCI->SD CARD or USB stick into account with=20 mirroring.=20 --=20 Regards, (jhell) Jason Hellenthal --jRHKVT23PllUwdXP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: http://bit.ly/0x89D8547E iQEcBAEBAgAGBQJNyw/5AAoJEJBXh4mJ2FR+besH/39USB9nnfhl5wL/rH+i7lpY 7lWVW48D0V8kbb2IAOSyGkIrUsvBqdHWmS6FJ5aYPzcrQVJg/ipiuY9c4n/SB9yy k7wF4PgU3uFFyluEKofsRLFtccCd+a5+U5QEdgoT2HXtcI6SNC0tk6dwUJL1M0uu Rzc3g7RQWF1hauDna7Mle13G43iQQThOTnpzWFVQFISQv3Nve/pYUVVXKKwS5e+n g+pS6NkImO6pb070BrAEwv4H4Xm0VBaFRIi2qV1Uc0J350vXjNIfWMBEO6Q4JNWV vBATQh7xR/OyttVXfAVnaohxdKsYhr34VqDdHjfSCsRlPZaH0ifSq6C0QLQeFhk= =o/7q -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP--