From owner-freebsd-stable@freebsd.org Wed Mar 8 07:10:24 2017 Return-Path: Delivered-To: freebsd-stable@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 0EC25D0271D for ; Wed, 8 Mar 2017 07:10:24 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) 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 E39711212 for ; Wed, 8 Mar 2017 07:10:23 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: by mailman.ysv.freebsd.org (Postfix) id E3004D0271C; Wed, 8 Mar 2017 07:10:23 +0000 (UTC) Delivered-To: stable@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 E2AF0D0271B for ; Wed, 8 Mar 2017 07:10:23 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (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 C282E1211 for ; Wed, 8 Mar 2017 07:10:23 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=CkfF+uKTZtqdpMlMDRuZTA25kH9f6T2bhYUtc0z4c3U=; b=IGwjltdB+pDVkAFqdJhze1OHLx 6Ee1GlOMYPS1S+my8VIaeYRdlp/ks4QB9mCu/NDf93HLwO3Y9eXHWCFRvnJpwYI6vBIQRX/SdiHDf gvPG3+BlpkQ5CUUq+eKNf+x6TQnwvOlCJQotcmCQ/STVfpsjaY9zcz6hTfKRbNAamFuI=; Received: from [114.125.80.198] (port=21841 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from ) id 1clVjj-000iiw-Uj; Wed, 08 Mar 2017 00:10:16 -0700 Date: Wed, 8 Mar 2017 15:10:10 +0800 From: Erich Dollansky To: Kevin Oberman Cc: "stable@freebsd.org" , Ian Smith Subject: Re: slow machine, swap in use, but more than 5GB of RAM inactive Message-ID: <20170308151010.0fa0d2dd@X220.alogt.com> In-Reply-To: References: <20170307101935.4c04ad5e@X220.alogt.com> <20170307232423.G87835@sola.nimnet.asn.au> <20170308071428.5f50167c@X220.alogt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Authenticated-Sender: sl-508-2.slc.westdc.net: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Mar 2017 07:10:24 -0000 Hi, On Tue, 7 Mar 2017 16:46:21 -0800 Kevin Oberman wrote: > On Tue, Mar 7, 2017 at 3:14 PM, Erich Dollansky > > wrote: > > > On Tue, 7 Mar 2017 23:30:58 +1100 (EST) > > Ian Smith wrote: > > > > > On Tue, 7 Mar 2017 10:19:35 +0800, Erich Dollansky wrote: > > > > > > > > I wonder about the slow speed of my machine while top shows > > > > ample inactive memory: > > > > > > ( quoting from this top output because it's neater :) > > > > > > > last pid: 85287; load averages: 2.56, 2.44, 1.68 > > > > up 6+10:24:45 10:13:36 191 processes: 5 running, 186 sleeping > > > > CPU 0: 47.1% user, 0.0% nice, 51.4% system, 0.0% interrupt, > > > > 1.6% idle CPU 1: 38.4% user, 0.0% nice, 60.4% system, 0.0% > > > > interrupt, 1.2% idle CPU 2: 38.8% user, 0.0% nice, 59.2% > > > > system, 0.0% interrupt, 2.0% idle CPU 3: 45.5% user, 0.0% > > > > nice, 51.0% system, 0.4% interrupt, 3.1% idle Mem: 677M > > > > Active, 5600M Inact, 1083M Wired, 178M Cache, 816M Buf,301M > > > > Free Swap: 16G Total, 1352M Used, 15G Free, 8% Inuse > > > > > > Others have covered the swap / inactive memory issue. > > > > > > But I'd expect this to be slow, for any new work anyway .. there's > > > next to no idle on any CPU. I'd be asking, what's all of that > > > system usage? > > > > > this is building ports in the background. Still, used doing this > > ones a month, I know the feeling when the ports are updated. This > > one was really slow. Hopefully, it was just an unlucky coincidence. > > > > I rebooted meanwhile the machine. It is faster now, I would say, it > > is back to normal now. It did not come to its limits since the new > > start. It is now on: > > > > FreeBSD 10.3-STABLE #3 r314363 > > > > Erich > > > > Well, looks like over half of the CPU is running in system space and > that seems rather high for what I would assume is compilation. I > thinnk you will need to poke around with things like systat, and the > like to see just what the system is doing for 55% or so of all CPUs. > Since there doe snot seem to be a lot of IO or memory at issue, the > various command for those are probably not very interesting. Probably > not lock stats, either. > > This reminds me of when some operation (IIRC NFS related) was calling > system time routines that are fairly expensive on FreeBSD almost > continually. > -- There were one or two NFS clients connected but should have been idle. Both are on an older FreeBSD 12. Could it be caused by a Seagate 2TB 2 1/2" HD with 8GB SSD (ST2000LX001-1RG174)? The system behaved strangely when the disk was new. It seemed that the flash part was used at the beginning also for writing. It took then some times up to a minute before data could have been read again after prolonged write operations. The disk has now a transfer volume of some 5TB and did not show this behaviour for a few weeks. It is only hard for me to see why this happens. I use this machine since years. The only change was the disk. I know, things can happen. As I have rebooted the machine, I will keep this in mind and check also this direction when this happens again. Thanks! Erich