Date: Sun, 23 May 2021 11:59:16 -0700 From: John-Mark Gurney <jmg@funkthat.com> To: Michael Gmelin <freebsd@grem.de> Cc: tech-lists <tech-lists@zyxst.net>, freebsd-current@freebsd.org Subject: Re: tuning a zfs-mounted /var Message-ID: <20210523185916.GM14975@funkthat.com> In-Reply-To: <B961A8FE-CE78-4490-8E6D-1EBD771629D1@grem.de> References: <YKlNQG%2BAk0gsjebb@ceres.zyxst.net> <B961A8FE-CE78-4490-8E6D-1EBD771629D1@grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Gmelin wrote this message on Sat, May 22, 2021 at 21:13 +0200:
> > On 22. May 2021, at 20:32, tech-lists <tech-lists@zyxst.net> wrote:
> >
> > ???Hi,
> >
> > What options could one pass to zfs to speed it up to characteristics
> > favourable to what's usually in /var ? Like lots of fast writes, lots of
> > files smaller than what's on /usr, lots of file creation and deletion
> > but also quite a few files that might become large, like what's in
> > /var/log, things like that.
> >
>
> Make sure your pool (or at least the /var file system) has compression=lz4 and that atime is off, beyond that I wouldn???t bother to try to optimize manually there, unless you run a database like MySQL in /var/db/???, in which case setting a fixed record size might make sense.
And if you're running a db in /var, you should just create a new dataset
for the database instead of reuse /var's dataset, that way the fixed
record size does not cause problems for the rest of /var...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210523185916.GM14975>