public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lou Langholtz <ldl@aros.net>
To: Mark Peloquin <peloquin@austin.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linstab <linstab@osdl.org>,
	ltp-results <ltp-results@lists.sourceforge.net>
Subject: Re: [Fwd: [BENCHMARK] 2.5.73, -bk1, -bk2, -mm1 regression results]
Date: Wed, 25 Jun 2003 09:42:16 -0600	[thread overview]
Message-ID: <3EF9C2D8.5060801@aros.net> (raw)
In-Reply-To: <3EF9BF57.5090309@austin.ibm.com>

Mark Peloquin wrote:

> Nightly Regression Summary
> for
> 2.5.72 vs 2.5.73
>
>
> Benchmark         Pass/Fail   Improvements   Regressions       
> Results       Results   Summary
> ---------------   ---------   ------------   -----------   
> -----------   -----------   -------
>
> dbench.ext2           P            N              N             
> 2.5.72        2.5.73    report
> dbench.ext3           P            Y              N             
> 2.5.72        2.5.73    report
> dbench.jfs            P            N              N             
> 2.5.72        2.5.73    report
> dbench.reiser         P            N              N             
> 2.5.72        2.5.73    report
> dbench.xfs            P            N              N             
> 2.5.72        2.5.73    report
> kernbench             P            N              N             
> 2.5.72        2.5.73    report
> lmbench               P            Y              Y             
> 2.5.72        2.5.73    report
> rawiobench            P            N              Y             
> 2.5.72        2.5.73    report
> specjbb               P            Y              Y             
> 2.5.72        2.5.73    report
> specsdet              P            N              Y             
> 2.5.72        2.5.73    report
> tbench                P            Y              N             
> 2.5.72        2.5.73    report
> tiobench.ext2         P            N              N             
> 2.5.72        2.5.73    report
> tiobench.ext3         P            Y              Y             
> 2.5.72        2.5.73    report
> tiobench.jfs          P            N              N             
> 2.5.72        2.5.73    report
> tiobench.reiser       P            Y              Y             
> 2.5.72        2.5.73    report
> tiobench.xfs          P            N              Y             
> 2.5.72        2.5.73    report
> volanomark            P            N              N             
> 2.5.72        2.5.73    report
>
> http://ltcperf.ncsa.uiuc.edu/data/2.5.73/2.5.72-vs-2.5.73/
>
> Nightly Regression Summary
> for . . .

Wow! This is impressive. I'd love to see this include performance of 
ext3 (or jfs) over NBD (network block device) too. Or at least 
performance metrics like this for NBD some other way. I've done some 
benchmarking myself for the work I've been doing on NBD but nothing near 
this comprehensive. If someone had the spare time to do this though for 
NBD, it'd help me enormously. Any interest??? :-)


      reply	other threads:[~2003-06-25 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 15:27 [Fwd: [BENCHMARK] 2.5.73, -bk1, -bk2, -mm1 regression results] Mark Peloquin
2003-06-25 15:42 ` Lou Langholtz [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=3EF9C2D8.5060801@aros.net \
    --to=ldl@aros.net \
    --cc=linstab@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-results@lists.sourceforge.net \
    --cc=peloquin@austin.ibm.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