All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miguel Figueiredo <elmig@debianpt.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	ck@vds.kolivas.org
Subject: call for more SD versus CFS comparisons (was: Re: [ck] Mainline plans)
Date: Tue, 12 Jun 2007 01:30:25 +0100	[thread overview]
Message-ID: <466DE921.9030709@debianpt.org> (raw)

Hi all,

some results based on massing_intr.c by Satoru, can be found on
http://people.redhat.com/mingo/cfs-scheduler/tools/massive_intr.c

Runned several times like:
$ massing_intr 5 2 >> results-kernel-5.2
$ massing_intr 300 300 >> results-kernel-300.300

To calculate average and standard deviation:

$ original-awk -f awkscript results-file

awkscript file included.
(for debian users: apt-get install original-awk)

Here's the data, values and facts:

kernel                  run as  average stddev
======                  ======  ======= ======
2.6.22-rc4-ck1          5 2     34      0
2.6.22-rc4-ck1          5 2     22      0
2.6.22-rc4-ck1          5 2     24.6    0.219
2.6.22-rc4-ck1          5 2     31.4    0.219
2.6.22-rc4-ck1          5 2     40      0

2.6.22-rc4-cfs-v16      5 2     36      0
2.6.22-rc4-cfs-v16      5 2     30      0
2.6.22-rc4-cfs-v16      5 2     27.6    0.219
2.6.22-rc4-cfs-v16      5 2     29.6    0.219
2.6.22-rc4-cfs-v16      5 2     42      0

2.6.22-rc4-cfs-v16      300 300 126.427 0.289
2.6.22-rc4-cfs-v16      300 300 125.35  0.275
2.6.22-rc4-cfs-v16      300 300 127,797 0,028
2.6.22-rc4-cfs-v16      300 300 125,367 0,028
2.6.22-rc4-cfs-v16      300 300 125,213 0,024

2.6.22-rc4-ck1          300 300 125.413 0,028
2.6.22-rc4-ck1          300 300 125,34  0,027
2.6.22-rc4-ck1          300 300 124,69  0,027
2.6.22-rc4-ck1          300 300 125,093 0,017
2.6.22-rc4-ck1          300 300 125,597 0,028

* "run as" it's the parameters passed to the program massive_intr.

All the files and data can be found on
http://www.debianpt.org/~elmig/pool/kernel/20070611/

Just one note, the first time this test was run:
-cfs-v16 i got this values: 44, 23, 19, 16, 42;
-2.6.21-debian: 29, 25, 22, 16, 32;
-ck1: 37 37 37 37 37

The machine was a Sempron64 3.0 GHz.


I know that other people, who read lkml, also tested the same way, it
would be nice if they also post their data.

-- 

Com os melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org


             reply	other threads:[~2007-06-12  0:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  0:30 Miguel Figueiredo [this message]
2007-06-12  7:39 ` call for more SD versus CFS comparisons (was: Re: [ck] Mainline plans) Tobias Gerschner
2007-06-12  8:36   ` Ingo Molnar
2007-06-12  8:51     ` Tobias Gerschner
2007-06-12  8:55       ` Ingo Molnar
2007-06-12  8:57     ` Ingo Molnar
2007-06-12 10:33       ` Con Kolivas
2007-06-12 10:40         ` Ingo Molnar
2007-06-12 14:04   ` Ingo Molnar
2007-06-12 16:52 ` Martin Steigerwald
2007-06-15 21:19   ` Miguel Figueiredo
2007-06-13  1:36 ` Fortier,Vincent [Montreal]
2007-06-13  1:54   ` Fortier,Vincent [Montreal]
2007-06-14  7:56     ` call for more SD versus CFS comparisons (was: " Jarek Poplawski
  -- strict thread matches above, loose matches on Subject: below --
2007-06-14 10:10 call for more SD versus CFS comparisons (was: Re: [ck] " Tobias Gerschner

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=466DE921.9030709@debianpt.org \
    --to=elmig@debianpt.org \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.