From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 03:48:20 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 73957215 for ; Mon, 21 Jul 2014 03:48:20 +0000 (UTC) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F33B2E28 for ; Mon, 21 Jul 2014 03:48:19 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.7/8.14.7) with ESMTP id s6L3mHeZ020807; Sun, 20 Jul 2014 23:48:17 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.7/8.14.4/Submit) id s6L3mHnF020806; Sun, 20 Jul 2014 23:48:17 -0400 (EDT) (envelope-from wollman) Date: Sun, 20 Jul 2014 23:48:17 -0400 (EDT) From: Garrett Wollman Message-Id: <201407210348.s6L3mHnF020806@hergotha.csail.mit.edu> To: jdc@koitsu.org Subject: Re: Consistently "high" CPU load on 10.0-STABLE X-Newsgroups: mit.lcs.mail.freebsd-stable In-Reply-To: <20140720235945.GA90603@icarus.home.lan> References: <20140720062413.GA56318@icarus.home.lan> Organization: none X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (hergotha.csail.mit.edu [127.0.0.1]); Sun, 20 Jul 2014 23:48:17 -0400 (EDT) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on hergotha.csail.mit.edu Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2014 03:48:20 -0000 In article <20140720235945.GA90603@icarus.home.lan> you write: >Yeah, I've given that a try. I think all that script does, in layman's >terms, is count the number of occurrences of a kernel function/symbol >being called. I've had good results in the past using pmcstat(8) in "top" mode. Of course you'll need a kernel with the PMC support compiled in to use that, and a CPU where hwpmc(4) supports a useful counter -- I'd start with something that counts unhalted cycles or retired instructions. -GAWollman