From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 2 11:35:57 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C096816A4CF for ; Wed, 2 Feb 2005 11:35:57 +0000 (GMT) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 344CD43D5E for ; Wed, 2 Feb 2005 11:35:57 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with SMTP id 65C4146B4D; Wed, 2 Feb 2005 06:35:56 -0500 (EST) Date: Wed, 2 Feb 2005 11:35:11 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Borja Marcos In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: Devilator - performance monitoring for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 11:35:57 -0000 On Wed, 2 Feb 2005, Borja Marcos wrote: > I'm not sure about the correct values in the process description > to get a picture as accurate as possible of the cpu usage of different > processes. I've seen that top uses p_runtime (FreeBSD 5 and FreeBSD 4), > but I'm not sure if the value would be really useful. This is very cool. :-) How are you currently extracting the information? One of the things I've wanted to do for a while is make sure all this sort of thing is exposed via snmpd so that the information can be gathered easily across a large number of hosts (say, 10,000). > BTW, I'm having serious issues with a machine with very big > directories, and I've been playing with the dirhash configuration, > setting up a very big cache. It would be useful to have some statistics > so that I can plot the number of hits/misses to that dirhash cache, etc. systat contains a large number of useful statistics and monitoring pieces, including some really useful stuff in systat -vmstat. There's also a lot of interesting information to be had from vmstat -z and vmstat -m in terms of tracking system resource use. It would be neat to have interrupt rates classified by source, so that the regularity of clock interrupts was visible against the variation in things like disk and network interrupts. Robert N M Watson