From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Theurer <habanero@us.ibm.com>,
Andrew Morton <akpm@digeo.com>,
William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.38-mm2 dbench $N times
Date: Wed, 25 Sep 2002 13:57:22 -0700 [thread overview]
Message-ID: <253480000.1032987442@flay> (raw)
In-Reply-To: <200209251351.58355.habanero@us.ibm.com>
> Pretty sure each dbench child does it's own write/read to only it's own data.
> There is no sharing that I am aware of between the processes.
Right, but if the processes migrate easily, there's still no CPU locality.
Bill, do you want to try binding 1/32 of the processes to each CPU, and see if
that makes your throughput increase?
> How about running in tmpfs to avoid any disk IO at all?
As far as I understand it, that won't help - we're operating out of pagecache anyway
at this level, I think.
> Also, what's the policy for home node assignment on fork? Are all of these
> children getting the same home node assingnment??
Policy is random - the scheduler lacks any NUMA comprehension at the moment.
The numa sched mods would probably help a lot too.
M.
next prev parent reply other threads:[~2002-09-25 20:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 13:20 2.5.38-mm2 dbench $N times William Lee Irwin III
2002-09-24 17:47 ` Andrew Morton
2002-09-25 0:18 ` William Lee Irwin III
2002-09-25 0:25 ` William Lee Irwin III
2002-09-25 0:31 ` Andrew Morton
2002-09-25 0:39 ` William Lee Irwin III
2002-09-25 0:46 ` Andrew Morton
2002-09-25 1:08 ` Dave Hansen
2002-09-25 1:17 ` William Lee Irwin III
2002-09-25 6:03 ` Martin J. Bligh
2002-09-25 18:51 ` Andrew Theurer
2002-09-25 20:57 ` Martin J. Bligh [this message]
2002-09-25 21:05 ` Andrew Theurer
2002-09-25 23:57 ` William Lee Irwin III
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=253480000.1032987442@flay \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=habanero@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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