Date: Thu, 24 Sep 2015 16:53:24 -0400 From: Quartz <quartz@sneakertech.com> To: FreeBSD questions <freebsd-questions@freebsd.org> Subject: Re: sync vs async vs zfs Message-ID: <560462C4.6030106@sneakertech.com> In-Reply-To: <98BFE313-523F-4A2C-82BB-8683466068FB@kraus-haus.org> References: <56042774.6070404@sneakertech.com> <98BFE313-523F-4A2C-82BB-8683466068FB@kraus-haus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Very short answer… OK, thanks. So far that lines up with what I thought I knew. I still think I might be fuzzy on what constitutes an 'app' in this context though, presumably you're also counting services like nfs, etc? Basically, when considering just boring file copies, which things are or are not async and when? Under what circumstances is sync actually used in the real world? >you can > use a device which is much faster than the main zpool devices Also 1) A SLOG's only purpose is to reduce fragmentation and increase sync speed, correct? Re: speed, using a SLOG that's the same speed as the other drives in a pool is mostly pointless, right? 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?560462C4.6030106>