From: Andrew Morton <akpm@osdl.org>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: davej@redhat.com, axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [patch] optimization: defer bio_vec deallocation
Date: Tue, 29 Mar 2005 01:15:47 -0800 [thread overview]
Message-ID: <20050329011547.249167e7.akpm@osdl.org> (raw)
In-Reply-To: <200503290307.j2T37Yg25879@unix-os.sc.intel.com>
"Chen, Kenneth W" <kenneth.w.chen@intel.com> wrote:
>
> On Mon, Mar 28, 2005 at 06:38:23PM -0800, Chen, Kenneth W wrote:
> > We have measured that the following patch give measurable performance gain
> > for industry standard db benchmark. Comments?
>
> Dave Jones wrote on Monday, March 28, 2005 7:00 PM
> > If you can't publish results from that certain benchmark due its stupid
> > restrictions, could you also try running an alternative benchmark that
> > you can show results from ?
> >
> > These nebulous claims of 'measurable gains' could mean anything.
> > I'm assuming you see a substantial increase in throughput, but
> > how much is it worth in exchange for complicating the code?
>
> Are you asking for micro-benchmark result?
There are a number of test tools floating about. reaim, orasim, osdb, others.
A number of them are fairly crufty and toy-like, but still more useful than
microbenchmarks, and they permit others to evaluate patches and to perform
further optimisation.
It's in everyone's interest that we get away from a test which has such
dopey restrictions.
prev parent reply other threads:[~2005-03-29 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 2:38 Chen, Kenneth W
2005-03-29 2:59 ` Dave Jones
2005-03-29 3:07 ` Chen, Kenneth W
2005-03-29 8:13 ` Jens Axboe
2005-03-29 18:44 ` Chen, Kenneth W
2005-03-29 18:48 ` Dave Jones
2005-03-30 10:30 ` Jens Axboe
2005-03-29 9:15 ` Andrew Morton [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=20050329011547.249167e7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=davej@redhat.com \
--cc=kenneth.w.chen@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®