From: Nish Aravamudan <nish.aravamudan@gmail.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: LKML List <linux-kernel@vger.kernel.org>
Subject: Re: load average wraps at 1024
Date: Wed, 11 Jan 2006 15:01:30 -0800 [thread overview]
Message-ID: <29495f1d0601111501j5c52b847v92bc95253513c280@mail.gmail.com> (raw)
In-Reply-To: <9a8748490601111440m53fdab80pfefc10efb214f3bd@mail.gmail.com>
On 1/11/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> Hi,
>
> Don't know if this is a kernel issue or userspace issue, but load
> average values wrap back to 0 once they hit 1024.
>
> I've been trying to stress 2.6.15-mm3 by putting a *lot* of load on it
> and seeing if it stays alive, how it copes, how long it seems to take
> to recover etc.
> While doing that I've done some test runs that start thousands of
> processes and the load average quickly shoots up to several hundred
> and eventually reach 1000 - when it continues to climb it goes to 1023
> and then wraps down to small numbers like 4-5 and then continue
> climbing from there. Once I kill all my processes it slowly goes down
> to zero, then wraps back to ~1000 and continues to climb down from
> there until it's eventually back to normal.
>
> Is this expected behaviour?
I'm going to say yes, based on the comments in sched.h:
/*
* These are the constant used to fake the fixed-point load-average
* counting. Some notes:
* - 11 bit fractions expand to 22 bits by the multiplies: this gives
* a load-average precision of 10 bits integer + 11 bits fractional
* - if you want to count load-averages more often, you need more
* precision, or rounding will get you. With 2-second counting freq,
* the EXP_n values would be 1981, 2034 and 2043 if still using only
* 11 bit fractions.
*/
That is, 10 bits of integer is 1024, the remaining 11 bits being used
for fractions.
Thanks,
Nish
prev parent reply other threads:[~2006-01-11 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 22:40 Jesper Juhl
2006-01-11 23:01 ` Nish Aravamudan [this message]
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=29495f1d0601111501j5c52b847v92bc95253513c280@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=jesper.juhl@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
all inboxes | Powered by JetHome®