All of lore.kernel.org
 help / color / mirror / Atom feed
From: rwhron@earthlink.net
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, ltp-list@lists.sourceforge.net
Subject: Re: I/O tests using elvtune to improve interactive performance
Date: Mon, 19 Nov 2001 10:26:09 -0500	[thread overview]
Message-ID: <20011119102609.A3713@earthlink.net> (raw)
In-Reply-To: <138.49c8e42.29247804@aol.com> <20011117030611.A214@earthlink.net> <20011119080922.S11826@suse.de>
In-Reply-To: <20011119080922.S11826@suse.de>; from axboe@suse.de on Mon, Nov 19, 2001 at 08:09:22AM +0100

On Mon, Nov 19, 2001 at 08:09:22AM +0100, Jens Axboe wrote:
> > Test:	Run growfiles tests from Linux Test Project that really hurt
> > 	interactive performance.  Simultaneously run "ls -laR /".
> > 	Change the elevator read latency value with elvtune.
> > 	Also run mp3blaster tests.
> 
> Interesting tests, thanks. I wonder if you could be convinced to do
> bonnie++ and dbench tests with the same read_latency values used? Also,
> I'm assuming you kept write latency at its default of 16384?
> -- 
> Jens Axboe
> 

Thanks for the feedback.  Write latency was 16384 for all tests.

I'm downloading dbench and bonnie++ now.   I'll check them out.

I'm still not sure how to measure/quantify interactive performance.  

My ideal test will have these components:

1) Simulate and measure user interactive response time.
2) Disk I/O patterns capable of making interactive performance slow.
3) Measurement of I/O throughput.
4) Note how changes with elvtune effect throughput and response time.
5) It's not too boring.  (i.e. type something, use a stop watch).

It's the "measure interactive response time" that I haven't got a handle 
on yet.  I'm looking at the SSBA benchmarks for something that simulates 
users.  I don't know if it measures response time.

I could resort to a stopwatch to test interactive response, but
hopefully, something better will come to mind.
-- 
Randy Hron


  reply	other threads:[~2001-11-19 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <138.49c8e42.29247804@aol.com>
2001-11-17  8:06 ` I/O tests using elvtune to improve interactive performance rwhron
2001-11-19  7:09   ` Jens Axboe
2001-11-19 15:26     ` rwhron [this message]
2001-11-20  7:32     ` rwhron

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=20011119102609.A3713@earthlink.net \
    --to=rwhron@earthlink.net \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-list@lists.sourceforge.net \
    /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.