From owner-freebsd-performance@FreeBSD.ORG Thu Jan 24 09:09:32 2008 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7814E16A419; Thu, 24 Jan 2008 09:09:32 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from proxypop1.sarenet.es (proxypop1.sarenet.es [194.30.0.99]) by mx1.freebsd.org (Postfix) with ESMTP id 4137613C474; Thu, 24 Jan 2008 09:09:31 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from localhost (matahari.sarenet.es [192.148.167.18]) by proxypop1.sarenet.es (Postfix) with ESMTP id E6F135D57; Thu, 24 Jan 2008 09:53:10 +0100 (CET) Message-Id: <3B3710F8-9308-48E1-AD0A-CF707A6898B6@SARENET.ES> From: Borja Marcos To: Kris Kennaway In-Reply-To: <47972895.4050005@FreeBSD.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Thu, 24 Jan 2008 09:53:11 +0100 References: <4796C717.9000507@cederstrand.dk> <47972895.4050005@FreeBSD.org> X-Mailer: Apple Mail (2.915) Cc: freebsd-performance@freebsd.org Subject: Re: Performance Tracker project update X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2008 09:09:32 -0000 On Jan 23, 2008, at 12:44 PM, Kris Kennaway wrote: > One suggestion I have is that as more metrics are added it becomes > important for an "at a glance" overview of changes so we can monitor > for performance improvements and regressions among many workloads. > > One way to do this would be a matrix of each metric with its change > compared to recent samples. e.g. you could do a student's T > comparison of today's numbers with those from yesterday, or from a > week ago, and colour-code those that show a significant deviation > from "no change". This might be a bit noisy on short timescales, so > you could aggregrate data into larger bins and compare e.g. moving 1- > week aggregates. Fluctuations on short timescales won't stand out, > but if there is a real change then it will show up less than a week > later. And now for some publicity :) I am a big fan of Orca (www.orcaware.com) which I have used regularly with Solaris *and* FreeBSD. I wrote a performance data collector for FreeBSD, actually. The advantage of Orca is that it gets simple text files with the performance data and then it generates graphs and web pages periodically, keeping the data in RRD databases. I think Orca would be really useful for this project. And of course, if anyone wants to give "Devilator" a try, it currently graphs CPU usage in system, interrupt, user time, disk I/O bandwidth, memory usage, system and SWI CPU usage, process sleeping reasons... So far it's been really helpful for me in order to identify bottlenecks. Regards, Borja.