LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] scheduler: strange behavor with massive interactive processes
Date: Sat, 31 Mar 2007 17:16:24 +0900	[thread overview]
Message-ID: <87y7ldhlpj.wl%takeuchi_satoru@jp.fujitsu.com> (raw)
In-Reply-To: <874po6tbez.wl%takeuchi_satoru@jp.fujitsu.com>

Hi Ingo,

> > > Hi Ingo and all,
> > > 
> > > When I was executing massive interactive processes, I found that some 
> > > of them occupy CPU time and the others hardly run.
> > 
> > yeah.
> > 
> > > I also attach the test program which easily recreates this problem.
> > 
> > thanks, this is really helpful - does the patch below improve the 
> > situation?

I tested your patch and it seems to work well.

Test environment
================

 - kernel: 2.6.21-rc5 with or without Ingo's patch
 - others: same as my initial mail except for omitting nice 19 cases

Result (without Ingo's patch)
=============================

  +---------+-----------+------+------+------+--------+
  |   # of  |   # of    | avg  | max  | min  |  stdev |
  |   CPUs  | processes | (*1) | (*2) | (*3) |  (*4)  |
  +---------+-----------+------+------+------+--------+
  | 1(i386) |       200 |  162 | 8258 |    1 |   1113 |
  +---------+-----------+------+------+------+--------+
  |         |           |  378 | 9314 |    2 |   1421 |
  | 2(ia64) |       400 +------+------+------+--------+
  |         |           |  189 |12544 |    1 |   1443 |
  +---------+-----------+------+------+------+--------+

  *1) average number of loops among all processes
  *2) maximum number of loops among all processes
  *3) minimum number of loops among all processes
  *4) standard deviation

Result (with Ingo's patch)
==========================

  +---------+-----------+------+------+------+--------+
  |   # of  |   # of    | avg  | max  | min  |  stdev |
  |   CPUs  | processes |      |      |      |        |
  +---------+-----------+------+------+------+--------+
  | 1(i386) |       200 |  153 |  232 |  128 |   7.67 |
  +---------+-----------+------+------+------+--------+
  |         |           |  376 |  451 |  291 |   17.6 |
  | 2(ia64) |       400 +------+------+------+--------+
  |         |           |  188 |  236 |  137 |   14.5 |
  +---------+-----------+------+------+------+--------+

Although it is not perfectly fair, it is certain that this patch really improve
the situation in dramatic form. Thank you very much!

Satoru

      reply	other threads:[~2007-03-31  8:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27  1:34 [BUG] scheduler: strange behavor with massive interactive processes Satoru Takeuchi
2007-03-27  5:04 ` Mike Galbraith
2007-03-28  8:38   ` Mike Galbraith
2007-03-28 11:45     ` Ingo Molnar
2007-03-28 11:51       ` Mike Galbraith
2007-03-31 10:15     ` Satoru Takeuchi
2007-03-31 10:29       ` Mike Galbraith
2007-03-27 19:14 ` Ingo Molnar
2007-03-28  1:16   ` Satoru Takeuchi
2007-03-31  8:16     ` Satoru Takeuchi [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=87y7ldhlpj.wl%takeuchi_satoru@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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;
as well as URLs for NNTP newsgroup(s).