All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Nate Diller <nate.diller@gmail.com>
Cc: Mike Benoit <ipso@snappymail.ca>, reiserfs-list@namesys.com
Subject: Re: Utilizing OSDL's STP for Reiser4 testing/benchmarks?
Date: Fri, 21 Jul 2006 23:57:59 -0600	[thread overview]
Message-ID: <44C1BE67.6020901@namesys.com> (raw)
In-Reply-To: <5c49b0ed0607212117v5465a928we762dbb5406cb173@mail.gmail.com>

Nate Diller wrote:

> On 7/21/06, Mike Benoit <ipso@snappymail.ca> wrote:
>
>> Has the Reiser4 team looked at utilizing the OSDL Scalable Test Platform
>> (STP) service to benchmark and test Reiser4 patches? They seem to offer
>> a wide variety of hardware to test on, and already have some file system
>> benchmarks available to choose from.
>>
>> I noticed the Namesys benchmark page hasn't been updated in quite some
>> time, understandably so, as benchmarking can be incredibly time
>> consuming.  Perhaps using the STP would make this much easier to do more
>> frequently?
>>
>> It would be really nice to see how the batch_write/read(?) patches to
>> the kernel affect things, and how Reiser4 performance progresses over
>> time. I know Hans has mentioned CPU usage dropping in recent patches,
>> but actual numbers from a benchmark are usually more compelling to see.
>
>
> the dev team has seen a number of benchmarks which Hans' statements
> are based on... maybe we should post some of them publicly?
>
> NATE
>
>
Sure.  I asked for that, actually.

      reply	other threads:[~2006-07-22  5:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21 16:06 Utilizing OSDL's STP for Reiser4 testing/benchmarks? Mike Benoit
2006-07-21 19:13 ` Hans Reiser
2006-07-22  4:17 ` Nate Diller
2006-07-22  5:57   ` Hans Reiser [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=44C1BE67.6020901@namesys.com \
    --to=reiser@namesys.com \
    --cc=ipso@snappymail.ca \
    --cc=nate.diller@gmail.com \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.