Date: Fri, 24 Feb 2012 12:21:38 +0000 From: Tom Evans <tevans.uk@googlemail.com> To: Luke Marsden <luke-lists@hybrid-logic.co.uk> Cc: freebsd-fs@freebsd.org, team@hybrid-logic.co.uk Subject: Re: Another ZFS ARC memory question Message-ID: <CAFHbX1KPW%2B4h2-LHE9rB0aVRqw%2BAzVDrjjVB2CCt=7T4JB8C3A@mail.gmail.com> In-Reply-To: <1330081612.13430.39.camel@pow> References: <1330081612.13430.39.camel@pow>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 24, 2012 at 11:06 AM, Luke Marsden <luke-lists@hybrid-logic.co.uk> wrote: > Hi all, > > Just wanted to get your opinion on best practices for ZFS. > > We're running 8.2-RELEASE v15 in production on 24GB RAM amd64 machines > but have been having trouble with short spikes in application memory > usage resulting in huge amounts of swapping, bringing the whole machine > to its knees and crashing it hard. =C2=A0I suspect this is because when t= here > is a sudden spike in memory usage the zfs arc reclaim thread is unable > to free system memory fast enough. > > This most recently happened yesterday as you can see from the following > munin graphs: > > E.g. http://hybrid-logic.co.uk/memory-day.png > =C2=A0 =C2=A0 http://hybrid-logic.co.uk/swap-day.png > > Our response has been to start limiting the ZFS ARC cache to 4GB on our > production machines - trading performance for stability is fine with me > (and we have L2ARC on SSD so we still get good levels of caching). > > My questions are: > > =C2=A0 =C2=A0 =C2=A0* is this a known problem? > =C2=A0 =C2=A0 =C2=A0* what is the community's advice for production machi= nes running > =C2=A0 =C2=A0 =C2=A0 =C2=A0ZFS on FreeBSD, is manually limiting the ARC c= ache (to ensure > =C2=A0 =C2=A0 =C2=A0 =C2=A0that there's enough actually free memory to ha= ndle a spike in > =C2=A0 =C2=A0 =C2=A0 =C2=A0application memory usage) the best solution to= this > =C2=A0 =C2=A0 =C2=A0 =C2=A0spike-in-memory-means-crash problem? > =C2=A0 =C2=A0 =C2=A0* has FreeBSD 9.0 / ZFS v28 solved this problem? > =C2=A0 =C2=A0 =C2=A0* rather than setting a hard limit on the ARC cache s= ize, is it > =C2=A0 =C2=A0 =C2=A0 =C2=A0possible to adjust the auto-tuning variables t= o leave more free > =C2=A0 =C2=A0 =C2=A0 =C2=A0memory for spiky memory situations? =C2=A0e.g.= set the auto-tuning to > =C2=A0 =C2=A0 =C2=A0 =C2=A0make arc eat 80% of memory instead of ~95% lik= e it is at > =C2=A0 =C2=A0 =C2=A0 =C2=A0present? > =C2=A0 =C2=A0 =C2=A0* could the arc reclaim thread be made to drop ARC pa= ges with > =C2=A0 =C2=A0 =C2=A0 =C2=A0higher priority before the system starts swapp= ing out > =C2=A0 =C2=A0 =C2=A0 =C2=A0application pages? > > Thank you for any/all answers, and thank you for making FreeBSD > awesome :-) It's not a problem, it's a feature! By default the ARC will attempt to cache as much as it can - it assumes the box is a ZFS filer, and doesn't need RAM for applications. The solution, as you've found out, is to limit how much ARC can take up. In practice, you should be doing this anyway. You should know, or have an idea, of how much RAM is required for the applications on that box, and you need to limit ZFS to not eat into that required RAM. Cheers Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFHbX1KPW%2B4h2-LHE9rB0aVRqw%2BAzVDrjjVB2CCt=7T4JB8C3A>