From owner-freebsd-questions@freebsd.org Fri Sep 25 02:05:39 2015 Return-Path: Delivered-To: freebsd-questions@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 38B3FA08427 for ; Fri, 25 Sep 2015 02:05:39 +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 183621903 for ; Fri, 25 Sep 2015 02:05:38 +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 B2D823F73C for ; Thu, 24 Sep 2015 22:05:36 -0400 (EDT) Message-ID: <5604ABF0.3060007@sneakertech.com> Date: Thu, 24 Sep 2015 22:05:36 -0400 From: Quartz MIME-Version: 1.0 To: FreeBSD questions Subject: Re: sync vs async vs zfs References: <56042774.6070404@sneakertech.com> <98BFE313-523F-4A2C-82BB-8683466068FB@kraus-haus.org> <560462C4.6030106@sneakertech.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 02:05:39 -0000 > I expect that system utilities like cp and tar do not do sync writes. > sync writes are supposed to be a special case, used only when needed. > I run into them with VBox writing to<>.vmdk files. NFS forces sync though, doesn't it? What if you're cp-ing to a mounted share? I'm not sure I totally understand how all this interacts. >> 2) Async doesn't really care how your pool is constructed, and a >> SLOG is really the only thing that seriously makes a difference for >> sync, correct? > > Not quite true. Once you get through the ARC the configuration of the > zpool _will_ matter to performance. Maybe I worded that badly. What I meant was that whereas sync write performance is strongly affected by a SLOG, async writes have no special considerations of their own that don't also affect sync, right?