Date: Mon, 18 Jun 2018 14:10:31 +0100 From: tech-lists <tech-lists@zyxst.net> To: freebsd-stable@freebsd.org Subject: Re: lightly loaded system eats swap space Message-ID: <de7c99ef-3bc4-54d5-26a9-acbfa0fe140b@zyxst.net> In-Reply-To: <CA%2BtpaK1hGsHLarvJ_1sEpjZ9bwL-zDNbnR%2BPX9BWOfNq6MXN_A@mail.gmail.com> References: <c8277497-ffcf-0503-490b-96d1b4605af7@zyxst.net> <20180618160855.44d9a0c2.freebsd.ed.lists@sumeritec.com> <ab5d0cb0-13f5-5de8-6189-c0a5c621c6e9@zyxst.net> <CA%2BtpaK1hGsHLarvJ_1sEpjZ9bwL-zDNbnR%2BPX9BWOfNq6MXN_A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18/06/2018 13:45, Adam wrote: > What is the output of sysctl vm.overcommit? That's a sysctl I've not heard of. It's 0 on both machines > If this system is intended on being a VM host, then why don't you > limit ARC to something reasonable like Total Mem - Projected VM Mem - > Overhead = Ideal ARC . I'll try doing that when I can take the machine out of service. thanks, -- J.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?de7c99ef-3bc4-54d5-26a9-acbfa0fe140b>