public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: Chris Friesen <cfriesen@nortel.com>,
	linux-kernel@vger.kernel.org, mingo@elte.hu,
	a.p.zijlstra@chello.nl, pj@sgi.com,
	Balbir Singh <balbir@in.ibm.com>,
	aneesh.kumar@linux.vnet.ibm.com
Subject: Re: fair group scheduler not so fair?
Date: Fri, 30 May 2008 15:51:21 +0530	[thread overview]
Message-ID: <20080530102121.GG12836@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080530064324.GA29381@linux.vnet.ibm.com>

On Fri, May 30, 2008 at 12:13:24PM +0530, Dhaval Giani wrote:
> > Also, although the long-term results are good, the shorter-term fairness 
> > isn't great.  Is there a tuneable that would allow for a tradeoff between 
> > performance and fairness?  I have people that are looking for within 4% 
> > fairness over a 1sec interval.
> >
> 
> How fair does smp fairness look for a !group scenario? I don't expect
> group schould be able to do much better.

Just tested this combo for !group case:

	1 nice0 (weight = 1024)
	2 nice3 (each weight = 526)
	3 nice5 (each weight = 335)

You'd expect nice0 to get (on a 2 cpu system):

	2 * 1024 / (1024 + 2*526 + 3*335) = 66.47

This is what I see over a 10sec interval (error = 6%):

 4386 root      20   0  1384  228  176 R 60.4  0.0   3:06.75  1 nice0
 4387 root      23   3  1384  232  176 R 37.9  0.0   1:57.03  0 nice3
 4388 root      23   3  1384  228  176 R 37.9  0.0   1:57.24  0 nice3
 4390 root      25   5  1384  228  176 R 24.1  0.0   1:14.62  0 nice5
 4391 root      25   5  1384  228  176 R 19.8  0.0   1:01.26  1 nice5
 4389 root      25   5  1384  228  176 R 19.7  0.0   1:01.12  1 nice5

Over 120sec interval (error still as high as 6%):

 4386 root      20   0  1384  228  176 R 60.4  0.0   6:13.95  1 nice0
 4388 root      23   3  1384  228  176 R 37.9  0.0   3:54.69  0 nice3
 4387 root      23   3  1384  232  176 R 37.9  0.0   3:54.44  0 nice3
 4390 root      25   5  1384  228  176 R 24.2  0.0   2:29.45  0 nice5
 4391 root      25   5  1384  228  176 R 19.8  0.0   2:02.56  1 nice5
 4389 root      25   5  1384  228  176 R 19.8  0.0   2:02.44  1 nice5

The high error could be because of interference from other tasks. Anyway I 
dont think !group case is better at achieving fairness over shorter
intervals.


-- 
Regards,
vatsa

  reply	other threads:[~2008-05-30 10:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 23:59 fair group scheduler not so fair? Chris Friesen
2008-05-22  6:56 ` Peter Zijlstra
2008-05-22 20:02   ` Chris Friesen
2008-05-22 20:07     ` Peter Zijlstra
2008-05-22 20:18       ` Li, Tong N
2008-05-22 21:13         ` Peter Zijlstra
2008-05-23  0:17           ` Chris Friesen
2008-05-23  7:44             ` Srivatsa Vaddagiri
2008-05-23  9:42         ` Srivatsa Vaddagiri
2008-05-23  9:39           ` Peter Zijlstra
2008-05-23 10:19             ` Srivatsa Vaddagiri
2008-05-23 10:16               ` Peter Zijlstra
2008-05-27 17:15 ` Srivatsa Vaddagiri
2008-05-27 18:13   ` Chris Friesen
2008-05-28 16:33     ` Srivatsa Vaddagiri
2008-05-28 18:35       ` Chris Friesen
2008-05-28 18:47         ` Dhaval Giani
2008-05-29  2:50         ` Srivatsa Vaddagiri
2008-05-29 16:46         ` Srivatsa Vaddagiri
2008-05-29 16:47           ` Srivatsa Vaddagiri
2008-05-29 21:30           ` Chris Friesen
2008-05-30  6:43             ` Dhaval Giani
2008-05-30 10:21               ` Srivatsa Vaddagiri [this message]
2008-05-30 11:36             ` Srivatsa Vaddagiri
2008-06-02 20:03               ` Chris Friesen
2008-05-27 17:28 ` Srivatsa Vaddagiri

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=20080530102121.GG12836@linux.vnet.ibm.com \
    --to=vatsa@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=balbir@in.ibm.com \
    --cc=cfriesen@nortel.com \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pj@sgi.com \
    /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