Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 08 Sep 2018 16:13:17 -0700
From:      Cy Schubert <Cy.Schubert@cschubert.com>
To:        Matthew Macy <mat.macy@gmail.com>
Cc:        Cy Schubert <Cy.Schubert@cschubert.com>, Jakob Alvermark <jakob@alvermark.net>, Mark Johnston <markj@freebsd.org>, Subbsd <subbsd@gmail.com>, "allanjude@freebsd.org" <allanjude@freebsd.org>, freebsd-current Current <freebsd-current@freebsd.org>
Subject:   Re: ZFS perfomance regression in FreeBSD 12 APLHA3->ALPHA4
Message-ID:  <201809082313.w88NDH3T059295@slippy.cwsent.com>
In-Reply-To: Message from Matthew Macy <mat.macy@gmail.com> of "Sat, 08 Sep 2018 12:49:31 -0700." <CAPrugNrjoYJxkYkdYikFC9eiK45ucL-bw6=zrFDMVWXZE2LvnA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In message <CAPrugNrjoYJxkYkdYikFC9eiK45ucL-bw6=zrFDMVWXZE2LvnA@mail.gma
il.com>
, Matthew Macy writes:
>
> On Sat, Sep 8, 2018 at 11:03 Cy Schubert <Cy.Schubert@cschubert.com> wrote:
>
> > In message <e5abddc5-17f0-bf5f-753b-1edbc9356385@alvermark.net>, Jakob
> > Alvermar
> > k writes:

> > >
> > > I will test the patch below and report back.
> >
> > Agreed, though IMO your workload and your environment need to be
> > understood first. What concerns me about the patch is what impact will
> > it have on other workloads. Not evicting data and only metadata could
> > impact buildworld -DNO_CLEAN for example. I do a -DNO_CLEAN
> > buildworlds, sometimes -DWORLDFAST. Adjusting vfs.zfs.arc_meta_limit to
> > the same value as vfs.zfs.arc_max improved my buildworld/installworld
> > performance. In addition disabling atime for the ZFS dataset containing
> > /usr/obj also improved buildworld/installworld performance by reducing
> > unnecessary (IMO) metadata writes. I think evicting metadata only might
> > cause a new set of problems for different workloads. (Maybe this should
> > be a sysctl?)
> >
>
> Mark's suggested change would just restore the default behavior from before
> balanced pruning was imported. Balanced pruning is dependent on code that
> didn't exist in FreeBSD - unfortunately when I did the import I did not
> pull in all the dependencies. Mid freeze, the least disruptive path is to
> disable the new behavior. Post branch we can restore it as a default,
> possibly contingent on the amount of memory in the system. There is
> precedent for this with prefetch.

Ok.


-- 
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  http://www.FreeBSD.org

	The need of the many outweighs the greed of the few.






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201809082313.w88NDH3T059295>