From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Mon, 1 Mar 2010 13:00:40 -0500 To: lucio@proxima.alt.za, 9fans@9fans.net Message-ID: In-Reply-To: <8bedeb6480059bea89539741b190d3f9@proxima.alt.za> References: <8bedeb6480059bea89539741b190d3f9@proxima.alt.za> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Interrupt saturation Topicbox-Message-UUID: de168e76-ead5-11e9-9d60-3106f5b1d025 On Mon Mar 1 12:53:59 EST 2010, lucio@proxima.alt.za wrote: > > workstation only? I.e. it is not running venti? > > Thanks for the chance to follow up. I implemented quanstro's > enhancement to /proc, and this is what I get right now, some > twenty-four hours after starting up: > > 50 18 76160483 clock > 65 1 15761 kbd > 73 11 9799735 ether0 > 89 3 124777 ac97audio > 145 12 213171 kbdaux > > The stuff Erik displayed looked a lot worse, so maybe it's just that > I'm not used to having stats(1) display a solid block for the > Interrupts. Still, I wish cpu cycles could be better utilised. > > And, tes, it's effectively a diskless terminal. my machine has been up for 90+ days. looks like you just have HZ set to 1000. stats isn't counting on that. also, 113 ethernet interrupts/sec is a pretty good clip. - erik