Matt,
On Thu, Aug 06, 2009 at 11:28:50AM -0700, Matt Ingenthron wrote:
> > If ZFS is not beinng used significantly, then ARC
> > should not grow. ARC grows
> > based on the usage (ie. amount of ZFS files/data
> > accessed). Hence, if you are
> > sure that the ZFS usage is low, things should be
>
> Besides the /etc/system, you could also export all
> the pools, use mdb to
> set the same variable that /etc/system sets, and then
> import the pools
> again. Don't know of any other mechanism to limit
> ZFS's memory foot print.
>
> If you don't do ZFS boot, manually import the pools
> after t
On 08/06/09 14:28, Matt Ingenthron wrote:
If ZFS is not beinng used significantly, then ARC
should not grow. ARC grows
based on the usage (ie. amount of ZFS files/data
accessed). Hence, if you are
sure that the ZFS usage is low, things should be
fine.
I understand that it won't grow, but I want
> If ZFS is not beinng used significantly, then ARC
> should not grow. ARC grows
> based on the usage (ie. amount of ZFS files/data
> accessed). Hence, if you are
> sure that the ZFS usage is low, things should be
> fine.
I understand that it won't grow, but I want it to be smaller than the defaul
Matt,
On Wed, Aug 05, 2009 at 07:06:06PM -0700, Matt Ingenthron wrote:
> Hi,
>
> Other than modifying /etc/system, how can I keep the ARC cache low at boot
> time?
>
> Can I somehow create an SMF service and wire it in at a very low level to put
> a fence around ZFS memory usage before other s
Hi,
Other than modifying /etc/system, how can I keep the ARC cache low at boot time?
Can I somehow create an SMF service and wire it in at a very low level to put a
fence around ZFS memory usage before other services come up?
I have a deployment scenario where I will have some reasonably large
