From owner-freebsd-current@freebsd.org Tue Jun 26 22:23:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F2D9101E36A for ; Tue, 26 Jun 2018 22:23:00 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3F71D86F42 for ; Tue, 26 Jun 2018 22:23:00 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 0026C101E369; Tue, 26 Jun 2018 22:23:00 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2112101E367 for ; Tue, 26 Jun 2018 22:22:59 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7434A86F41 for ; Tue, 26 Jun 2018 22:22:59 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w5QMMqpJ030276 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Jun 2018 15:22:52 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w5QMMq9E030275; Tue, 26 Jun 2018 15:22:52 -0700 (PDT) (envelope-from sgk) Date: Tue, 26 Jun 2018 15:22:51 -0700 From: Steve Kargl To: Adrian Chadd Cc: Alexander Leidinger , "current@freebsd.org" Subject: Re: numa involved in instability and swap usage despite RAM free? Message-ID: <20180626222251.GA30202@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180624120329.Horde.HWORumQ7Ng1KAUeviJNtoc3@webmail.leidinger.net> <20180625182250.GA40651@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:23:00 -0000 On Tue, Jun 26, 2018 at 02:39:27PM -0700, Adrian Chadd wrote: > On Mon, 25 Jun 2018 at 11:23, Steve Kargl > wrote: > > > > On Sun, Jun 24, 2018 at 12:03:29PM +0200, Alexander Leidinger wrote: > > > > > > I don't have hard evidence, but there is enough "smell" to open up a > > > discussion... > > > > > > Short: > > > Can it be that enabling numa in the kernel is the reason why some > > > people see instability with zfs and usage of swap while a lot of free > > > RAM is available? > > > > Interesting observation. I do have NUMA in my kernel, and swap > > seems to be used instead of recycling freeing inactive memory. > > Top shows > > > > Mem: 506M Active, 27G Inact, 98M Laundry, 2735M Wired, 1474M Buf, 1536M Free > > Swap: 16G Total, 120M Used, 16G Free > > > > Perhaps, I don't understand what is meant by inactive memory. I > > thought that this means memory is still available in the buffer > > cache, but nothing is current using what is there. > > > > Aren't there now per-domain VM counters you can query via sysctl? > Maybe they'd help in diagnosing what's going on. > I upgraded to a r335642 yesterday. I haven't seen the swapping problem, yet; although I've tried to force it. There are 158 sysctl knobs that contain the string "vm". Do you have a pointer any particular one to monitor? -- Steve