From owner-freebsd-fs@freebsd.org Sun Sep 20 21:11:57 2015 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A716A05D85 for ; Sun, 20 Sep 2015 21:11: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 4BF541E22 for ; Sun, 20 Sep 2015 21:11:56 +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]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by douhisi.pair.com (Postfix) with ESMTPSA id C693F3F6FD for ; Sun, 20 Sep 2015 17:11:49 -0400 (EDT) Message-ID: <55FF2115.8010209@sneakertech.com> Date: Sun, 20 Sep 2015 17:11:49 -0400 From: Quartz MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: Re: ZFS cpu requirements, with/out compression and/or dedup References: <55FF111A.4040300@kateley.com> In-Reply-To: <55FF111A.4040300@kateley.com> Content-Type: text/plain; charset=ISO-8859-1; 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: Sun, 20 Sep 2015 21:11:57 -0000 > Any algorithm for TB's of storage and cpu/ram is usually wrong. dedup is kind of a special case though, because it has to keep the entire DDT in non-paged ram (assuming you want the machine to be usable). Of course, the rule of thumb is for USED space. 40TB of blank space won't need any ram obviously.