LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: akpm@linux-foundation.org, Bill Irwin <bill.irwin@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
arjan@linux.intel.com
Subject: Re: [PATCH (update 3)] timer: Run calc_load halfway through each round_jiffies second
Date: Fri, 2 Mar 2007 19:03:56 +0100 [thread overview]
Message-ID: <200703021903.56720.dada1@cosmosbay.com> (raw)
In-Reply-To: <45E85FC3.801@simon.arlott.org.uk>
On Friday 02 March 2007 18:32, Simon Arlott wrote:
> On 02/03/07 16:35, Eric Dumazet wrote:
> > You could just change LOAD_FREQ from (5*HZ) to (5*HZ+1)
> > You can see that 5.01 instead of 5.00 second gives the same EXP_xx
> > values.
> >
> > So (5*HZ + 1) is safe. (because HZ >= 100)
>
> On HZ=1000, this would cause the load average to be pushed towards +1.00
> for up to 2 minutes every ~83 minutes with no obvious cause. (If a task
> takes ~10-20ms to run, so 20 runs are needed at HZ=1000 before it passes
> it again).
Nope, you dont quite understand how load (avenrun[]) is computed.
Every 5 seconds, three values are adjusted, based on their previous value and
the actual value. Lets focus on the first value (mean load average on one
minute)
exp = 1.0 / exp(5.0/60.0);
avenrun[0] = (avenrun[0] * exp) + (active * (1.0 - exp));
If previous value is 0.0, and current active count 1, then next value for
avenrun[0] will be : 0.0799556
Not exactly 1.0 as you think !
Then in the next intervals (if active count is 0), it will decrease 'slowly' :
0.0735627
0.0676809
0.0622695
0.0572907
In average, your load factor close to reality.
Just try my suggestion, it should work. I even proved it in my previous
mail :)
Eric
next prev parent reply other threads:[~2007-03-02 18:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 15:19 round_jiffies and load average Simon Arlott
2007-03-01 9:11 ` Simon Arlott
2007-03-01 18:52 ` [PATCH] timer: Add an initial 0.5s delay to calc_load Simon Arlott
2007-03-01 22:52 ` [PATCH (updated)] timer: Run calc_load halfway through each round_jiffies second Simon Arlott
2002-01-01 3:05 ` Pavel Machek
2007-03-05 22:35 ` Simon Arlott
2007-03-06 18:42 ` [PATCH (update 4)] " Simon Arlott
2007-03-06 22:20 ` [PATCH (updated)] " Chuck Ebbert
2007-03-01 23:10 ` Bill Irwin
2007-03-02 10:15 ` [PATCH (update 2)] " Simon Arlott
2007-03-02 15:15 ` [PATCH (update 3)] " Simon Arlott
2007-03-02 16:35 ` Eric Dumazet
2007-03-02 17:32 ` Simon Arlott
2007-03-02 18:03 ` Eric Dumazet [this message]
2007-03-02 20:14 ` Simon Arlott
2007-03-02 22:32 ` Eric Dumazet
2007-03-02 23:54 ` Simon Arlott
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=200703021903.56720.dada1@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=bill.irwin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@fire.lp0.eu \
--subject='Re: [PATCH (update 3)] timer: Run calc_load halfway through each round_jiffies second' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).