From owner-freebsd-fs@freebsd.org Sun Jan 3 19:20:52 2016 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 66244A5FB15 for ; Sun, 3 Jan 2016 19:20:52 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A69B1B24 for ; Sun, 3 Jan 2016 19:20:51 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id u03JKcLb023682; Sun, 3 Jan 2016 13:20:38 -0600 (CST) Date: Sun, 3 Jan 2016 13:20:38 -0600 (CST) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: "Mikhail T." cc: freebsd-fs@freebsd.org Subject: Re: NFS reads vs. writes In-Reply-To: <56895E2E.8060405@aldan.algebra.com> Message-ID: References: <568880D3.3010402@aldan.algebra.com> <56895E2E.8060405@aldan.algebra.com> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Sun, 03 Jan 2016 13:20:38 -0600 (CST) 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, 03 Jan 2016 19:20:52 -0000 On Sun, 3 Jan 2016, Mikhail T. wrote: > > Why would the same ZFS -- with the same slog -- be working faster, when written to locally, than when over NFS? Yes (it depends). Normal local writes are async writes so they do not use the slog at all. NFS writes are usually synchronous writes so they hit the slog hard. You would need software which intentionally issues synchronous writes to local disks in order to test synchronous local writes. Write sizes of 128k and above are written directly to pool disks and don't go to the slog, even if they are sync writes. This is done to make sure that the slog does not limit pool performance due to bandwidth limitations (vs IOPS). Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/