mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Kravetz <kravetz@us.ibm.com>
To: Robert Love <rml@tech9.net>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Scheduler Cleanup
Date: Wed, 5 Dec 2001 14:48:41 -0800	[thread overview]
Message-ID: <20011205144841.E1193@w-mikek2.des.beaverton.ibm.com> (raw)
In-Reply-To: <20011126114610.B1141@w-mikek2.des.beaverton.ibm.com> <Pine.LNX.4.33.0111280145300.3429-100000@localhost.localdomain> <20011205135851.D1193@w-mikek2.des.beaverton.ibm.com> <1007590396.28567.6.camel@phantasy>
In-Reply-To: <1007590396.28567.6.camel@phantasy>; from rml@tech9.net on Wed, Dec 05, 2001 at 05:13:14PM -0500

On Wed, Dec 05, 2001 at 05:13:14PM -0500, Robert Love wrote:
> Ehh, odd.  How does the dropped performance compare to MQ performance
> before 2.4.16?  In other words, are we solving problems in the newer
> kernels and now MQ is becoming overhead?

No I don't think that is the case.  The throughput numbers for this
benchmark at one specific data point on an 8-way look like.

2.4.14 Default Scheduler    39463
2.4.14 MQ Scheduler        385687
2.4.16 Default Scheduler    51364
2.4.16 MQ Scheduler        240667

The MQ numbers are still quite a bit better even on 2.4.16.  I can
easily get MQ 2.4.16 back up to MQ 2.4.14 levels by reintroducing the
code to give a slight preference to the currently running task.
However, our MQ scheduler is trying to closely match the behavior of
the default scheudler wherever possible (for better or worse).  It
should also be noted that performance of the default scheduler
increased as a result of Ingo's changes.

It is entirely possible that there is some other bug/feature in our
MQ code that is causing this situation.  As mentioned by others, the
scheduler code that was removed from 2.4.15 should have little if
any impact on performance.  I need to do some more analysis here.

-- 
Mike

      reply	other threads:[~2001-12-05 22:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 19:46 Mike Kravetz
2001-11-26 20:49 ` Davide Libenzi
2001-11-27 20:57   ` Shaya Potter
2001-11-27 21:53     ` george anzinger
2001-11-28  1:07 ` Ingo Molnar
2001-12-05 21:58   ` Mike Kravetz
2001-12-05 23:44     ` Davide Libenzi
2001-12-05 23:46       ` Mike Kravetz
2001-12-06  0:26         ` Davide Libenzi
2001-12-06 10:38         ` Ingo Molnar
2001-12-06 18:25           ` Davide Libenzi
2001-12-06 22:03             ` Ingo Molnar
2001-12-06 20:36               ` Davide Libenzi
2001-12-08 16:36     ` The best VM algorithm for Linux Martin Devera
2001-12-05 22:13   ` Scheduler Cleanup Robert Love
2001-12-05 22:48     ` Mike Kravetz [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=20011205144841.E1193@w-mikek2.des.beaverton.ibm.com \
    --to=kravetz@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rml@tech9.net \
    /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®