From owner-freebsd-questions Sat Jun 1 02:59:34 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA05473 for questions-outgoing; Sat, 1 Jun 1996 02:59:34 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA05407 for ; Sat, 1 Jun 1996 02:59:05 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id ae13343; 1 Jun 96 10:58 +0100 Received: from longacre.demon.co.uk ([158.152.156.24]) by relay-3.mail.demon.net id aa01887; 1 Jun 96 10:58 +0100 From: Michael Searle Message-ID: To: questions@freefall.freebsd.org Subject: Re: Excessive interrupts question References: <199605311756.KAA26673@freefall.freebsd.org> Date: Fri, 31 May 1996 21:04:28 BST X-Mailer: Offlite 0.09 / Termite Internet for Acorn RISC OS Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk robmel@nadt.org.uk (Robin Melville) wrote: > OK, I installed the new xperfmon++ ... it works fine. However, it is > still showing very high interrupt levels which don't tally with the > vmstat -i report. > xperfmon++ run as an X-client on the problem machine still shows > interrupts as hovering around 20 000 per second while vmstat shows > around 120/sec. > Is your program measuring something different from vmstat? > Best regards, > Robin. In an earlier post, vmstat -i output showed an unusually low number of clock interrupts. (but otherwise normal.) Maybe if the system clock used by xperfmon++ is slow, a normal interrupt rate is shown as being very high. (20 000 per 100 seconds or however long it takes for 100 ticks of the slow clock) -- Michael Searle - searle@longacre.demon.co.uk