From: Anton Blanchard <anton@samba.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: O(1) scheduler, 2.5.2-pre9-B1 results
Date: Sun, 6 Jan 2002 23:49:27 +1100 [thread overview]
Message-ID: <20020106124927.GA30292@krispykreme> (raw)
In-Reply-To: <Pine.LNX.4.33.0201060128250.1250-100000@localhost.localdomain> <Pine.LNX.4.33.0201060202590.2102-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0201060202590.2102-100000@localhost.localdomain>
Hi Ingo,
I got your scheduler rewrite going on ppc64. Here are some initial
LMbench results with sched-O1-2.4.17-B4.patch. Bear in mind the two
machines are different chips (one is Power3 and the other is RS64), so
some differences will result:
2 way (POWER3) summary:
signal handling down a bit (GOOD)
fork down a lot (very GOOD)
exec, sh down (GOOD)
context switches all down (GOOD)
communication latencies: Pipe, AF, TCP slightly up (BAD)
pipe bandwidth up (GOOD)
4 way (RS64) summary:
stat up a bit (BAD)
fork down a lot (very GOOD)
exec, sh down (GOOD)
context switches same or down (GOOD)
communication latencies: Pipe, AF, TCP slightly up (BAD)
pipe bandwidth up (GOOD)
So far things look good. Next up I'll look at how it scales on the 12
way.
Anton
next prev parent reply other threads:[~2002-01-06 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 0:38 [patch] O(1) scheduler, 2.4.17-B0, 2.5.2-pre8-B0 Ingo Molnar
2002-01-05 23:35 ` Pawel Kot
2002-01-06 1:04 ` [patch] O(1) scheduler, 2.5.2-pre9-B1 Ingo Molnar
2002-01-06 12:49 ` Anton Blanchard [this message]
2002-01-06 18:14 ` O(1) scheduler, 2.5.2-pre9-B1 results Ingo Molnar
2002-01-06 3:34 ` [patch] O(1) scheduler, 2.4.17-B0, 2.5.2-pre8-B0 listmail
2002-01-06 6:10 ` Robert Love
2002-01-06 22:48 ` Nathan
2002-01-08 16:54 ` george anzinger
2002-01-08 18:05 ` Rik van Riel
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=20020106124927.GA30292@krispykreme \
--to=anton@samba.org \
--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