Date: Wed, 17 Feb 2016 18:07:55 -0500 From: Brandon Allbery <allbery.b@gmail.com> To: hiren panchasara <hiren@strugglingcoder.info> Cc: "Efra?n D?ctor" <efraindector@motumweb.com>, owner-freebsd-stable@freebsd.org, "stable@freebsd.org" <stable@freebsd.org> Subject: Re: intr using Swap Message-ID: <CAKFCL4VQw5mFw5CEAVY5A-Yh8NYEDWAMR=ici53oDT7%2BJbi9Sg@mail.gmail.com> In-Reply-To: <20160217230138.GJ89208@strugglingcoder.info> References: <56C4AF81.3040202@motumweb.com> <87f6fb602e0ad11b7600c70a08d74c30@dweimer.net> <56C4C244.8070805@motumweb.com> <d6b6f3959b51a4ba3b8ab86de5931ae2@dweimer.net> <56C4F7E9.9090405@motumweb.com> <20160217230138.GJ89208@strugglingcoder.info>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 17, 2016 at 6:01 PM, hiren panchasara < hiren@strugglingcoder.info> wrote: > Yes, I've seen this too. Inact end up accumulating a very large chunk of > memory leaving Free to very low. > > What VM/pagedaemon seems to care about is Free+Cache and not just Free. > I kind of get that Free mem is wasted mem but putting everything in Inact > to the point that machine has to go into swap when a sudden need arises > also doesn't seem right. > If the file cache is "hot" but some working storage that was used at boot and will never be touched again is lying around (or, perhaps, that getty listening on a virtual console you never use), it makes perfect sense to push that out to swap. "Swap in use" does not mean "memory management problems". -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKFCL4VQw5mFw5CEAVY5A-Yh8NYEDWAMR=ici53oDT7%2BJbi9Sg>