From owner-freebsd-current@freebsd.org Sun Mar 13 15:24:40 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F8E1ACE70D for ; Sun, 13 Mar 2016 15:24:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDD74B8E; Sun, 13 Mar 2016 15:24:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x235.google.com with SMTP id n190so197057776iof.0; Sun, 13 Mar 2016 08:24:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=xkvt4YroQ0xEYDWXVEF23KY3VtmSfZhcfYFkuT7s/lQ=; b=xyo4yf74b0r3eeFWOnXvQmpMjJt0Rr3MuqrV2afIZEgGRA0o+/cbi3rZ5sZ9VSJ0xQ T+Z+5+yraM9d+UGjUPeqMWZEy79alCRn5J/0aC7DllXQ9xLuSidOpDz7jjild4P0spv4 GCt0ASl4Z7nr3pEVPsPLdjPQQQr7hlZT59TEVqk5InDSFY5992DFy0FQg2R1/0DLjN36 rSYiQgx7mQmFSNh3YZVP+k4FoBgoq9cPYAr+L9weG6BX6PX38uenlNRZihpuihLf92lz 0xnOxqHRQ56t1kocSLdIOoMMQmUkLg1gqYOOI/Ja3a62WxK8lt64JXi1aiDQLt7D6U5h m+tg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=xkvt4YroQ0xEYDWXVEF23KY3VtmSfZhcfYFkuT7s/lQ=; b=ICF33pQZuveC6gewAAZBbFkOLsAB8Y8+B9fl/3ZVHzbGNcGdmOWMqkP9Zj99JqD7qe wWC0Q6EE8eXX06pCEP35iW7Gx8Ag8y9MdyqpFeVLH/Fuv/C1oXy4SxCcQpH+tDyW6sz3 ImP+pjv8/DnpkoB9ApUEfnF4/7h+UBDRFClbVN2zOfpF7TldtO0bAXUHbmDhjh1XUdHs pzFDe+iEP0H+XucYK4TvD36dD1AmQ6c+L/Pf6v9rmOFopTD0dGXHOp0O/2YVyBG0BpBs IFnbHQTuMpVmPaRUVqLTob4uVrK3oQFW/ojFJPzT2l7v/tWLaQWdVGftgxIiFnMqb6qC 14Zg== X-Gm-Message-State: AD7BkJIkv41UKflip9p5901RK5BXw8ydYGKz8fSWV75kPGTPDXOdYwDlWnNEK5XdctpwLgWLbvyuCcseSlFpBA== MIME-Version: 1.0 X-Received: by 10.107.19.73 with SMTP id b70mr19218280ioj.75.1457882679055; Sun, 13 Mar 2016 08:24:39 -0700 (PDT) Received: by 10.36.14.19 with HTTP; Sun, 13 Mar 2016 08:24:38 -0700 (PDT) In-Reply-To: <20160313145548.4e011152@gumby.homeunix.com> References: <20160312093835.727d7197@ernst.home> <20160313145548.4e011152@gumby.homeunix.com> Date: Sun, 13 Mar 2016 08:24:38 -0700 Message-ID: Subject: Re: how to recycle Inact memory more aggressively? From: Adrian Chadd To: RW Cc: freebsd-current , Alan Cox Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2016 15:24:40 -0000 Yeah, but his comment is that "i'm doing a large file copy operation; why is the system paging out binaries versus recycling other file cache memory?" I have a feeling this is more due to the last few years of VM work to improve file serving performance and it hasn't really been tested/evaluated in desktop style environments where binary execution latency matters (ie, paging out binaries is a no-no.) Bugs have crept in and been fixed when people notice. :) I've noticed the same on my 8 and 16G desktop laptops but I haven't started digging into it. I was hoping it was going to be a VM bug versus something more structural in the VM changes. -a On 13 March 2016 at 07:55, RW wrote: > On Sat, 12 Mar 2016 09:38:35 +0100 > Gary Jennejohn wrote: > >> In the course of the last year or so the behavior of the vm system >> has changed in regard to how aggressively Inact memory is recycled. >> >> My box has 8GB of memory. At the moment I'm copying 100s of gigabytes >> from one file system to another one. >> >> Looking at top I observe that there are about 6GB of Inact memory. >> This value hardly changes. Instead of aggressively recycling the >> Inact memory the vm now seems to prefer to swap. > > Paging-out is a side-effect of processing inactive memory. As the > inactive queue is recycled a small number of pages can get copied > out to swap with the contents remaining in memory. If you turn this > off, the writes to can end up being done while something is waiting, > rather than in the background. > > A small amount of swap in use is normal. If you see a large amount > then check for memory leaks and unwanted files on tmpfs. > > > > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"