From: William Lee Irwin III <wli@holomorphy.com>
To: Hanna Linder <hannal@us.ibm.com>
Cc: Maneesh Soni <maneesh@in.ibm.com>, Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, viro@math.psu.edu
Subject: Re: 2.5.36-mm1 dbench 512 profiles
Date: Fri, 20 Sep 2002 13:39:38 -0700 [thread overview]
Message-ID: <20020920203938.GL3530@holomorphy.com> (raw)
In-Reply-To: <61200000.1032547873@w-hlinder>
On Fri, Sep 20, 2002 at 11:51:13AM -0700, Hanna Linder wrote:
> I mentioned it at OLS too. It was the point of my talk. Next
> time I will request a non 10am time slot!
10AM is relatively early in the morning for me. =)
On Friday, September 20, 2002 05:03:58 -0700 William Lee Irwin III <wli@holomorphy.com> wrote:
>> take its place. Ugly. OTOH the qualitative difference is striking. The
>> interactive responsiveness of the machine, even when entirely unloaded,
>> is drastically improved, along with such nice things as init scripts
>> and kernel compiles also markedly faster. I suspect this is just the
>> wrong benchmark to show throughput benefits with.
>> Also notable is that the system time was significantly reduced though
>> I didn't log it. Essentially a long period of 100% system time is
>> entered after a certain point in the benchmark, during which there are
>> few (around 60 or 70) context switches in a second, and the duration
>> of this period was shortened.
On Fri, Sep 20, 2002 at 11:51:13AM -0700, Hanna Linder wrote:
> Bill, you are saying that replacing dcache_rcu significantly
> improved system response time among other things?
> Perhaps it is time to reconsider replacing fastwalk with dcache_rcu.
> Viro? What are your objections?
Basically, the big ones get laggy, and laggier with more cpus. This fixed
a decent amount of that.
Another thing to note is that the max bandwidth of these disks is 40MB/s,
so we're running pretty close to peak anyway. I need to either get an FC
cable or something to see larger bandwidth gains.
Cheers,
Bill
next prev parent reply other threads:[~2002-09-20 20:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 22:30 2.5.36-mm1 dbench 512 profiles William Lee Irwin III
2002-09-19 23:18 ` Hanna Linder
2002-09-19 23:38 ` Andrew Morton
2002-09-19 23:45 ` Hanna Linder
2002-09-20 0:08 ` William Lee Irwin III
2002-09-20 4:02 ` William Lee Irwin III
2002-09-20 7:59 ` Maneesh Soni
2002-09-20 8:06 ` William Lee Irwin III
2002-09-20 12:03 ` William Lee Irwin III
2002-09-20 18:51 ` Hanna Linder
2002-09-20 20:32 ` Hanna Linder
2002-09-20 20:54 ` Dipankar Sarma
2002-09-20 20:39 ` William Lee Irwin III [this message]
2002-09-20 21:30 ` Martin J. Bligh
2002-09-20 23:11 ` William Lee Irwin III
2002-09-20 23:22 ` Martin J. Bligh
2002-09-21 7:52 ` William Lee Irwin III
2002-09-20 14:34 ` Dave Hansen
2002-09-20 16:07 ` Martin J. Bligh
2002-09-20 17:48 ` Dipankar Sarma
2002-09-20 17:40 ` Dipankar Sarma
2002-09-20 20:28 ` Dipankar Sarma
2002-09-20 5:14 ` William Lee Irwin III
2002-09-20 6:59 ` 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=20020920203938.GL3530@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=hannal@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=viro@math.psu.edu \
/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).