load average
I just rebooted ('cause I recompiled the kernel the other day) and restarted
KDE. When I do this on DFly and run top, the load average is about 1.5. When I
do it on Linux, the load average shoots up to 11 or 20 or higher. In both
OSes, the computer is slow to respond and makes lots of disk noises. I think
what's happening is, processes that are waiting for the disk are counted as
running in Linux but not in DFly. Is there a way to tell how busy the system
is that includes disk usage?
Pierre
--
I believe in Yellow when I'm in Sweden and in Black when I'm in Wales.
Re: load average
On Thu, 8 Mar 2012 14:15:16 -0500
Pierre Abbat p...@phma.optus.nu wrote:
I just rebooted ('cause I recompiled the kernel the other day) and
restarted KDE. When I do this on DFly and run top, the load average is
about 1.5. When I do it on Linux, the load average shoots up to 11 or 20
or higher. In both OSes, the computer is slow to respond and makes lots
of disk noises. I think what's happening is, processes that are waiting
for the disk are counted as running in Linux but not in DFly. Is there a
way to tell how busy the system is that includes disk usage?
You can use systat -v to get a very detailed picture of what's
going on with CPU, swap, disc activity, interrupts and VM activity.
--
Steve O'Hara-Smith | Directable Mirror Arrays
C:WIN | A better way to focus the sun
The computer obeys and wins.|licences available see
You lose and Bill collects. |http://www.sohara.org/
Re: How to suppress kernel hammer debug messages.
:Hello, : :I am new to this mailing list and was wondering if anyone could :help me figure out how to suppress or otherwise disable the logging of these :apparently benign debug messages that are filling up my syslog file. :. :hammer: debug: forcing async flush ip 0001093483e9... The debugging message was added to verify that a particular bug was being caught and fixed. It's one of several unconditional debugging kprintf()'s that could probably be stripped out from the code. There's no conditionalization on it. I will push a conditionalization of this particular message to master and the 3.0 release branches. Getting rid of them will require recompiling the kernel w/updated sources. Or you can just strip the related kprintf out yourself and recompile your kernel (the three lines at line 2438 of /usr/src/sys/vfs/hammer/hammer_inode.c if you have unpacked the sources should be where this kprintf() resides). -Matt Matthew Dillon dil...@backplane.com
