From owner-freebsd-current@freebsd.org Tue Mar 6 18:19:24 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 4202CF483A8 for ; Tue, 6 Mar 2018 18:19:24 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [199.15.120.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DCBFD8326F for ; Tue, 6 Mar 2018 18:19:23 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 3zwlFW3px3z19M for ; Tue, 6 Mar 2018 12:10:55 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3zwlFV5dfqz7Gs; Tue, 6 Mar 2018 12:10:54 -0600 (CST) Date: Tue, 6 Mar 2018 12:10:54 -0600 From: "Matthew D. Fuller" To: freebsd-current@FreeBSD.org Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT Message-ID: <20180306181054.GA42539@over-yonder.net> References: <20180305203918.jydrv7oelnh7sxp2@ler-imac.lerctr.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180305203918.jydrv7oelnh7sxp2@ler-imac.lerctr.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 06 Mar 2018 18:19:24 -0000 On Mon, Mar 05, 2018 at 02:39:18PM -0600 I heard the voice of Larry Rosenman, and lo! it spake thus: > > Yesterday, and I'm seeing really strange slowness, ARC use, and SWAP > use and swapping. > > Ideas? Since I updated to the Feb 25 -CURRENT I'm currently running (from mid-Sept, I believe), I see similar. It seems like the ARC has gotten really unwilling to yield, so it grows up in size, and then doesn't let up under pressure. I saw programs being actively used constantly swapping their working set in and out, since they were left with tiny available memory. Hard-slappping vfs.zfs.arc_max down a ways mitigated it enough to get me through the days, but is a pretty gross hackaround... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.