Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Aug 2010 23:05:56 -0700
From:      Jeremy Chadwick <freebsd@jdc.parodius.com>
To:        Matthias Gamsjager <mgamsjager@gmail.com>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: zfs arc - just take it all and be good to me
Message-ID:  <20100811060556.GA60029@icarus.home.lan>
In-Reply-To: <AANLkTi=BMXOnmT2CWBn62ysnQrAKcDq5EkAh-zYpM=9Q@mail.gmail.com>
References:  <20100810214418.GA28288@tolstoy.tols.org> <4C61F9CB.1010506@ukr.net> <AANLkTi=BMXOnmT2CWBn62ysnQrAKcDq5EkAh-zYpM=9Q@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 11, 2010 at 07:43:24AM +0200, Matthias Gamsjager wrote:
> > Please, insert into /boot/loader.conf only this options:
> > vm.kmem_size="999M"
> > vm.kmem_size_max="999M"
> > vfs.zfs.arc_max="160M"
> > vfs.zfs.prefetch_disable=1
> >
> > And after reboot, please run dd...
> 
> vfs.zfs.arc_max="160M" should be enough to limit the size of the arc.

That depends on exactly what date/time your kernel sources are, and what
tag/release you're running.  The ARC limiting feature was changed at one
point in time (from a "high watermark" to a hard-set limit).

The OP didn't include uname -a output, so we don't know what exact
version of the kernel/system he's running.

> and I'm not sure if that  ( vm.kmem_size="999M"
> ,vm.kmem_size_max="999M") is such a good idea.

Yes, it is a good idea.

And you shouldn't need to adjust vm.kmem_size_max, only vm.kmem_size.

-- 
| Jeremy Chadwick                                   jdc@parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |




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