Date: Mon, 15 Feb 2010 08:54:48 -0800 From: Artem Belevich <fbsdlist@src.cx> To: Alexander Leidinger <Alexander@leidinger.net> Cc: freebsd-stable@freebsd.org, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: hardware for home use large storage Message-ID: <ed91d4a81002150854w421b054oc81eb88ae767f5b4@mail.gmail.com> In-Reply-To: <20100215161105.14071eiflhc9le68@webmail.leidinger.net> References: <cf9b1ee01002150049o43fced71ucb5776a0a1eaf4cf@mail.gmail.com> <20100215090756.GA54764@icarus.home.lan> <20100215105000.101326yj01j0f64g@webmail.leidinger.net> <20100215122744.GA57382@icarus.home.lan> <20100215161105.14071eiflhc9le68@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>> * vm.kmem_size >> * vm.kmem_size_max > > I tried kmem_size_max on -current (this year), and I got a panic during u= se, > I changed kmem_size to the same value I have for _max and it didn't panic > anymore. It looks (from mails on the lists) that _max is supposed to give= a > max value for auto-enhancement, but at least it was not working with ZFS > last month (and I doubt it works now). It used to be that vm.kmem_size_max needed to be bumped to allow for larger vm.kmem_size. It's no longer needed on amd64. Not sure about i386. vm.kmem_size still needs tuning, though. While vm.kmem_size_max is no longer a limit, there are other checks in place that result in default vm.kmem_size being a bit on the conservative side for ZFS. >> Then, when it comes to debugging problems as a result of tuning >> improperly (or entire lack of), the following counters (not tunables) >> are thrown into the mix as "things people should look at": >> >> =A0kstat.zfs.misc.arcstats.c >> =A0kstat.zfs.misc.arcstats.c_min >> =A0kstat.zfs.misc.arcstats.c_max > > c_max is vfs.zfs.arc_max, c_min is vfs.zfs.arc_min. > >> =A0kstat.zfs.misc.arcstats.evict_skip >> =A0kstat.zfs.misc.arcstats.memory_throttle_count >> =A0kstat.zfs.misc.arcstats.size > > I'm not very sure about size and c... both represent some kind of current > size, but they are not the same. arcstats.c -- adaptive ARC target size. I.e. that's what ZFS thinks it can grow ARC to. It's dynamically adjusted based on when/how ZFS is back-pressured for memory. arcstats.size -- current ARC size arcstats.p -- portion of arcstats.c that's used by "Most Recently Used" items. What's left of arcstats.c is used by "Most Frequently Used" items. --Artem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ed91d4a81002150854w421b054oc81eb88ae767f5b4>