From: Jens Axboe <axboe@suse.de>
To: rwhron@earthlink.net
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 08:09:22 +0100 [thread overview]
Message-ID: <20011119080922.S11826@suse.de> (raw)
In-Reply-To: <138.49c8e42.29247804@aol.com> <20011117030611.A214@earthlink.net>
In-Reply-To: <20011117030611.A214@earthlink.net>
On Sat, Nov 17 2001, rwhron@earthlink.net wrote:
> Kernel: 2.4.15-pre5
>
> 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
next prev parent reply other threads:[~2001-11-19 7:10 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 [this message]
2001-11-19 15:26 ` rwhron
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=20011119080922.S11826@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=rwhron@earthlink.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox