Date: Mon, 2 Apr 2018 19:30:05 +0100 From: Stilez Stilezy <stilezy@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS dedup write pathway - possible inefficiency or..? Message-ID: <CAFwhr76%2B4G_ZVK1kHYvVegs1Oocdz3aPeqF3t%2BQtdsVmwtCmjg@mail.gmail.com> In-Reply-To: <14c857cc-463f-a56e-bcf6-c0702da6d3bc@FreeBSD.org> References: <CAFwhr76S-hqJya5P91HsJh94SnYR-scn%2BcmBEUFCDpQT_gD_OA@mail.gmail.com> <14c857cc-463f-a56e-bcf6-c0702da6d3bc@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks on that tip, Andriy, I don't have the knowledge to tell if that's the first of the 2 issues I'm seeing. It could be. What exactly is that bug describing and what behaviour would it create? Assuming it's the same - 1) Are there any known workarounds or sysctls that help to reduce the issue? 2) Are there any easy diagnostic tests I can easily do, to confirm if this is the same behaviour as that bug? Nobody else uses the test system, so I can change any sysctls to sane or extreme values for testing, or create large txg's and spread out reads and writes to see what's happening and what coincides with what. Thanks again On 2 April 2018 at 18:47, Andriy Gapon <avg@freebsd.org> wrote: > On 02/04/2018 16:36, Stilez Stilezy wrote: > > The first issue is specific to the > > dedup write pathway. I've tested locally to a point where it seems it's > > not due to inadequate hardware and it's very consistent and specific, > even > > on idle conditions/minimal load. I'm wondering whether there's a code > > bottleneck specifically affecting just the dedup write pathway. > > I think that this might be https://www.illumos.org/issues/8353 > > -- > Andriy Gapon >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFwhr76%2B4G_ZVK1kHYvVegs1Oocdz3aPeqF3t%2BQtdsVmwtCmjg>