From owner-freebsd-fs@FreeBSD.ORG Tue Sep 20 18:45:13 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 351AB1065677 for ; Tue, 20 Sep 2011 18:45:13 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by mx1.freebsd.org (Postfix) with ESMTP id DA3978FC1C for ; Tue, 20 Sep 2011 18:45:12 +0000 (UTC) Received: by vws5 with SMTP id 5so1176852vws.17 for ; Tue, 20 Sep 2011 11:45:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2yh1zGEglDQRK/+Q9i+GwUumWW9qwKPtvxFCKRTsIDM=; b=pCB1tKTSopVzOqgdnlIpWFvv4Obj3lbny17hHOn6ZlccFN0KlpNG+6mW1dbRGJntN6 8F02AEXZ4o0fHqdwnsLfP7R9b1UugGjgat3OINHoFjMUg5agl7BQ9UFk5EpmSBi0uOKZ 6WUZq8O9yNJRdx/ClExQnMsxxvZpgrBLrgSBg= MIME-Version: 1.0 Received: by 10.52.176.196 with SMTP id ck4mr1054023vdc.168.1316544311726; Tue, 20 Sep 2011 11:45:11 -0700 (PDT) Received: by 10.220.198.130 with HTTP; Tue, 20 Sep 2011 11:45:11 -0700 (PDT) In-Reply-To: References: <1316459220.35419.YahooMailClassic@web121209.mail.ne1.yahoo.com> Date: Tue, 20 Sep 2011 11:45:11 -0700 Message-ID: From: Freddie Cash To: Bob Friesenhahn Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS obn FreeBSD hardware model for 48 or 96 sata3 paths... 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: Tue, 20 Sep 2011 18:45:13 -0000 On Tue, Sep 20, 2011 at 9:01 AM, Bob Friesenhahn < bfriesen@simple.dallas.tx.us> wrote: > On Mon, 19 Sep 2011, Freddie Cash wrote: > >> >> L2ARC has extreme bandwidth limitations as compared with RAM. Be careful >> what you wish for. >> >> For writes (7 MBps, I believe); there shouldn't be any limits on the >> reads. >> > > If (for example) an SSD is used with a 200MB/s read rate for the L2ARC, > then the L2ARC is limited to 200MB/s (as compared with perhaps 10GB/s or > 20GB/s for RAM). > Ah, yes, obviously it's limited by the hardware, but so is the pool. :) I meant there's no artificial limits on reads from an L2ARC device, or writes to a ZIL device. In contrast to the write throttling for the L2ARC device. > The L2ARC is really all about eliminating the access latency of > rotating-rust but any device will provide far less bandwidth than system > RAM. > Yes, L2ARC is definitely slower than RAM. But properly selected/configured L2ARC will be a heck of a lot faster/lower latency than the pool. Hence the ordering I gave originally: ARC -> L2ARC -> pool -- Freddie Cash fjwcash@gmail.com