linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [patch] HT scheduler, sched-2.5.68-B2
Date: Wed, 23 Apr 2003 10:47:55 -0700	[thread overview]
Message-ID: <1535810000.1051120075@flay> (raw)
In-Reply-To: <Pine.LNX.4.44.0304231816210.10779-100000@localhost.localdomain>

>  - turn off the more agressive idle-steal variant. This could fix the
>    low-load regression reported by Martin J. Bligh.

Yup, that fixed it (I tested just your first version with just that
bit altered).

Thanks! 

M.


 DISCLAIMER: SPEC(tm) and the benchmark name SDET(tm) are registered
trademarks of the Standard Performance Evaluation Corporation. This 
benchmarking was performed for research purposes only, and the run results
are non-compliant and not-comparable with any published results.

Results are shown as percentages of the first set displayed

SDET 1  (see disclaimer)
                           Throughput    Std. Dev
                   2.5.68       100.0%         0.7%
                2.5.68-ht        72.9%         1.8%
           2.5.68-ht-pasv        98.4%         3.4%

SDET 2  (see disclaimer)
                           Throughput    Std. Dev
                   2.5.68       100.0%         2.8%
                2.5.68-ht        73.7%         2.1%
           2.5.68-ht-pasv       100.4%         1.0%

SDET 4  (see disclaimer)
                           Throughput    Std. Dev
                   2.5.68       100.0%         1.0%
                2.5.68-ht        62.5%        47.0%
           2.5.68-ht-pasv        99.7%         2.8%

SDET 8  (see disclaimer)
                           Throughput    Std. Dev
                   2.5.68       100.0%         0.6%
                2.5.68-ht        92.6%         1.0%
           2.5.68-ht-pasv       101.2%         1.7%

SDET 16  (see disclaimer)
                           Throughput    Std. Dev
                   2.5.68       100.0%         0.1%
                2.5.68-ht       100.0%         0.5%
           2.5.68-ht-pasv       101.1%         0.4%

SDET 32  (see disclaimer)
                           Throughput    Std. Dev
                   2.5.68       100.0%         0.4%
                2.5.68-ht        99.1%         0.6%
           2.5.68-ht-pasv        99.6%         0.6%

SDET 64  (see disclaimer)
                           Throughput    Std. Dev
                   2.5.68       100.0%         0.2%
                2.5.68-ht        99.0%         0.1%
           2.5.68-ht-pasv       100.3%         0.4%

SDET 128  (see disclaimer)
                           Throughput    Std. Dev
                   2.5.68       100.0%         0.1%
                2.5.68-ht        99.0%         0.1%
           2.5.68-ht-pasv        99.2%         1.3%



  reply	other threads:[~2003-04-23 17:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 16:23 [patch] HT scheduler, sched-2.5.68-B2 Ingo Molnar
2003-04-23 17:47 ` Martin J. Bligh [this message]
2003-04-23 17:53   ` Andrew Theurer
2003-04-23 18:43     ` Martin J. Bligh
2003-04-23 20:14       ` Andrew Theurer
2003-04-24  8:43         ` Rick Lindsley
2003-04-24 14:23           ` Andrew Theurer
2003-04-23 22:38       ` Martin J. Bligh
2003-04-24 21:29         ` Bill Davidsen
2003-04-24 22:39           ` Martin J. Bligh

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=1535810000.1051120075@flay \
    --to=mbligh@aracnet.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).