From: Bill Davidsen <davidsen@tmr.com>
To: "Theodore Tso" <tytso@mit.edu>,
"Bill Davidsen" <davidsen@tmr.com>,
linux-kernel@vger.kernel.org,
"Corrado Zoccolo" <czoccolo@gmail.com>,
"\"J.A. Magallón\"" <jamagallon@ono.com>,
"Jan Knutar" <jk-lkml@sci.fi>
Subject: Re: SSD and IO schedulers
Date: Fri, 10 Apr 2009 08:46:29 -0400 [thread overview]
Message-ID: <49DF3FA5.30705@tmr.com> (raw)
In-Reply-To: <20090410055725.GC10557@mit.edu>
Theodore Tso wrote:
> On Thu, Apr 09, 2009 at 07:56:32PM -0400, Bill Davidsen wrote:
>
>> This is good information, and if I ever configure a netbook for run
>> fsync-tester I shall avoid the DL scheduler. ;-(
>>
>> However... this test, and several others designed to find the ultimate
>> performance limits of disk io, don't mimic any typical use of most
>> desktops and virtually all netbooks.
>>
>> Is there a benchmark which would return so useful data for typical use,
>> doing some mail, some browsing, and maybe some light presentation,
>> spreadsheet, or word processing. None of those uses are likely to
>> generate this level of io, this file size, etc. The number of users is
>> one, it's not used as a server, and probably most of the tuning done (if
>> any) is aimed at battery life rather than blinding speed with a three
>> digit load average.
>>
>
> As long as you don't believe a netbook user will ever try to type an
> e-mail using a mail reader like alpine (which is what Linus uses),
> while running "yum update" in the background, sure. But if you don't
> think that is a normal use case, I'll let you argue with Linus on that
> score. In any case, the big-file-write-and-flush plus fsync-tester
> was designed to roughly replicate this scenario which Linus saw on his
> desktop system.
>
I almost fell out of my chair reading this, because I was doing exactly
what you describe, applying the latest Fedora 9 security stuff and
reading mail. The difference is that I'm not on a netbook, with a puny
CPU, small memory and 5400 rpm drive, but a VM running on a host with
multi-core, 8GB RAM, and a raid array of fast TB drives. The way I would
use a netbook would be as a glorified PDA, and I still feel that a
useful benchmark should duplicate the typical use, rather than some case
which occurs a few times a month, unless that case is the critical load
and justified less optimal performance the majority of the time.
Thanks for the history lesson, but I want my netbook to handle best the
stuff I do most. If the modified scheduler performed better when I am
reading mail and need to open a spreadsheet attachment, I'd certainly
prefer that. Whether I'd bother to build my own patched kernel would
depend on how "faster" it ran, I'm reasonably happy with the way that
runs on what I have.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
"You are disgraced professional losers. And by the way, give us our money back."
- Representative Earl Pomeroy, Democrat of North Dakota
on the A.I.G. executives who were paid bonuses after a federal bailout.
prev parent reply other threads:[~2009-04-10 12:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 21:55 SSD and IO schedulers Lorenzo Allegrucci
2009-01-31 8:45 ` Jens Axboe
2009-01-31 10:42 ` Alan Jenkins
2009-02-03 23:40 ` J.A. Magallón
2009-02-07 16:58 ` Jan Knutar
2009-04-08 19:18 ` Corrado Zoccolo
2009-04-08 19:56 ` Heinz Diehl
2009-04-08 20:18 ` Corrado Zoccolo
2009-04-09 10:33 ` Heinz Diehl
2009-04-09 10:50 ` Heinz Diehl
2009-04-09 23:56 ` Bill Davidsen
2009-04-10 5:57 ` Theodore Tso
2009-04-10 12:46 ` Bill Davidsen [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=49DF3FA5.30705@tmr.com \
--to=davidsen@tmr.com \
--cc=czoccolo@gmail.com \
--cc=jamagallon@ono.com \
--cc=jk-lkml@sci.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).