From: Rik van Riel <riel@redhat.com>
To: Ask List <askthelist@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Runnable threads on run queue
Date: Sun, 09 Jul 2006 04:33:19 -0400 [thread overview]
Message-ID: <44B0BF4F.7070102@redhat.com> (raw)
In-Reply-To: <loom.20060708T220409-206@post.gmane.org>
Ask List wrote:
> Have an issue maybe someone on this list can help with.
>
> At times of very high load the number of processes on the run queue drops to
> 0 then jumps really high and then drops to 0 and back and forth. It seems to
> last 10 seconds or so.
Are you using sendmail by any chance? :)
We start out with a low load averag, so sendmail forks as many
spamassassins as it can...
> procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
> r b swpd free buff cache si so bi bo in cs us sy id wa
> 83 0 1328 301684 37868 1520632 0 0 0 264 400 1332 98 2 0 0
> 17 0 1328 293936 37868 1520688 0 0 0 0 537 979 97 3 0 0
> 73 0 1328 293688 37868 1520712 0 0 0 0 268 2643 98 2 0 0
> 80 0 1328 277220 37868 1520756 0 0 0 0 351 824 98 2 0 0
> 49 0 1328 262452 37868 1520800 0 0 0 0 393 1882 97 3 0 0
> 45 0 1328 246796 37868 1520828 0 0 0 304 302 1631 96 4 0 0
> 55 0 1328 243852 37868 1520872 0 0 0 0 356 1101 99 1 0 0
> 17 0 1328 228672 37868 1520916 0 0 0 0 336 748 97 3 0 0
> 0 0 1328 299948 37868 1520956 0 0 0 0 299 821 78 3 19 0
> 0 0 1328 299184 37868 1520960 0 0 0 0 168 78 8 0 92 0
... and guess what?
The load average went through the roof, so sendmail stops forking
spamassassins. Now nothing is running, and sendmail will not start
forking new spamassassins again until after the load average has
decayed to an acceptable level.
After that, it will fork way too many at once again, and the load
average will go through the roof. Lather, rinse, repeat.
You'd probably be better off limiting the number of simultaneous
local mail deliveries to something reasonable, so the load average
always stays at an acceptable level - and more importantly, all of
the CPU capacity could be used if needed...
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
next prev parent reply other threads:[~2006-07-09 8:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 20:18 Runnable threads on run queue Ask List
2006-07-08 21:18 ` Chase Venters
2006-07-08 22:54 ` Ask List
2006-07-08 22:19 ` Dr. David Alan Gilbert
2006-07-08 23:08 ` Ask List
2006-07-09 7:20 ` Mike Galbraith
2006-07-09 23:38 ` Horst von Brand
2006-07-12 4:14 ` Ask List
2006-07-12 5:40 ` Mike Galbraith
2006-07-13 19:05 ` Ask List
2006-07-09 8:33 ` Rik van Riel [this message]
2006-07-12 3:55 ` Ask List
[not found] <fa.CQngdtRN/1xSBi2RLvhjLxBm1bE@ifi.uio.no>
2006-07-09 16:11 ` Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44B0BF4F.7070102@redhat.com \
--to=riel@redhat.com \
--cc=askthelist@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox