IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New try iowait
the load figure is a measure of how many processes are waiting to make use of the CPU, not how hard the CPU is working. A common reason for high load figures with nothing obvious going on is IO. Most often, harddrive IO. If one process is doing lots of small writes, things will start piling up quickly.

iowait is the IO equivalent of "top". You should be able to find out fairly quickly if IO wait is the cause of your high load figures.
New Command not found ... wtf?
And apt-cache search doesn't find anything for it. What package is it in?
--

Drew
New Argh! That should be "iotop"
My apologies for that one. It has its own package if not installed: iotop.
New Okay, installed
I keep seeing jdb2 every couple of seconds, then occasionally Firefox, syslog and flush.

Should that really be writing every couple of seconds? Seems excessive.
--

Drew
New Depends on what is being done
For me, on this site, Firefox doesn't do anything at all. If the page you're on has some type of Ajax script running, then whatever it downloads will cause disk access.

jdb2 is the ext4 journal. It would be normal for this to show up whenever some other program writes to disk. However, there does seem to be an ext4 bug with behavior that matches your description: https://bbs.archlinu...pic.php?id=113516. No clean cause there, but a few workarounds for specific users.

flush popping up is normal whenever something has been sent to disk. This is most likely triggered by the Firefox writes.
New Just changed my commit, will see what happens next reboot
--

Drew
New This is *VERY* similar to EXT3
and the IO bugs it had when it first did logging and journaling

Oh well.

Personally if its a laptop, I turn down the auto stuff... for the journaling to write every 5 seconds.
     Why would my load permantnely hover over 1? - (drook) - (14)
         Kernel drivers? - (Another Scott) - (1)
             One of the comments mentions overheating - (drook)
         top - (folkert) - (2)
             A bunch of small things - (drook) - (1)
                 What do the first 5 lines say? - (scoenye)
         try iowait - (scoenye) - (6)
             Command not found ... wtf? - (drook) - (5)
                 Argh! That should be "iotop" - (scoenye) - (4)
                     Okay, installed - (drook) - (3)
                         Depends on what is being done - (scoenye) - (2)
                             Just changed my commit, will see what happens next reboot -NT - (drook)
                             This is *VERY* similar to EXT3 - (folkert)
         Doesn't matter - (crazy) - (1)
             I don't run heavy stuff locally any more - (drook)

Your Bork God[tm] is HERE!
97 ms