From: Anton Blanchard <anton@linuxcare.com.au>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Only one memory zone for sparc64
Date: Sat, 17 Mar 2001 13:45:51 +1100 [thread overview]
Message-ID: <20010317134551.A3403@linuxcare.com> (raw)
In-Reply-To: <20010315191352.D1598@linuxcare.com> <20010316121654.C1771@redhat.com>
In-Reply-To: <20010316121654.C1771@redhat.com>; from sct@redhat.com on Fri, Mar 16, 2001 at 12:16:54PM +0000
> I'd be surprised if dbench was anything other than disk-bound on most
> systems. On any of my machines, the standard error of a single dbench
> run is *way* larger than 1%, and I'd expect to have to run the
> benchmark a dozen times to get a confidence interval small enough to
> detect a 1% performance change: are your runs repeatable enough to be
> this sensitive to the effect of the allocator?
With 2G RAM and:
kill -STOP <kupdated>
echo "90 64 64 256 5120 30720 95 0 0" > /proc/sys/vm/bdflush
I dont do one single disk interrupt for a dbench 60 :)
At this stage dbench runs become more repeatable.
Anton
prev parent reply other threads:[~2001-03-17 2:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 8:13 [PATCH]: Only one memory zone for sparc64 Anton Blanchard
2001-03-15 12:36 ` Rik van Riel
2001-03-16 12:16 ` Stephen C. Tweedie
2001-03-17 2:45 ` Anton Blanchard [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=20010317134551.A3403@linuxcare.com \
--to=anton@linuxcare.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.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