From: Paolo Valente <paolo.valente@unimore.it>
To: Aaron Carroll <aaronc@cse.unsw.edu.au>
Cc: Fabio Checconi <fchecconi@gmail.com>,
Jens Axboe <jens.axboe@oracle.com>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND][RFC] BFQ I/O Scheduler
Date: Thu, 17 Apr 2008 17:18:25 +0200 [thread overview]
Message-ID: <48076A41.5040806@unimore.it> (raw)
In-Reply-To: <48073F15.7070502@cse.unsw.edu.au>
Aaron Carroll ha scritto:
> You still end up with reduced global throughput as
> you've shown in the ``Short-term time guarantees'' table. It is an
> interesting case though... since the lower performance is not though
> fault
> of the process it doesn't seem fair to ``punish'' it.
Just a note about that table. The lower aggregate throughput of bfq is
due to the fact that, because of the higher number of movies being read,
a higher percentage of not-that-profitable accesses is being performed
under bfq wrt to cfq. As shown in the complete logs of the aggregate
throughput in the raw results, the aggregate throughput with bfq and cfq
is practically the same when the number of movies is the same.
The figure in the "Aggregate throughput" subsection is probably best
suited for a comparison of the performance of the two schedulers with
sequential accesses under the same conditions (the figure refers to the
2, 128 MB long, files, but we got virtually the same results in all the
other tests).
I do agree on that these experiments should be repeated with different
(faster) devices.
Paolo
>
> -- Aaron
>
>
next prev parent reply other threads:[~2008-04-17 15:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 15:29 [RESEND][RFC] BFQ I/O Scheduler Fabio Checconi
2008-04-15 8:22 ` Jens Axboe
2008-04-15 9:11 ` Fabio Checconi
2008-04-15 12:42 ` Jens Axboe
2008-04-15 18:08 ` Fabio Checconi
2008-04-16 6:48 ` Paolo Valente
2008-04-18 1:26 ` Aaron Carroll
2008-04-16 18:44 ` Pavel Machek
2008-04-17 6:14 ` Paolo Valente
2008-04-17 7:10 ` Jens Axboe
2008-04-17 8:26 ` Paolo Valente
2008-04-17 8:30 ` Jens Axboe
2008-04-17 9:24 ` Paolo Valente
2008-04-17 9:27 ` Jens Axboe
2008-04-17 10:19 ` Aaron Carroll
2008-04-17 10:21 ` Jens Axboe
2008-04-17 11:30 ` Fabio Checconi
2008-04-17 15:19 ` Avi Kivity
2008-04-17 15:47 ` Paolo Valente
2008-04-17 15:51 ` Avi Kivity
2008-04-17 18:12 ` Paolo Valente
2008-04-17 23:44 ` Aaron Carroll
2008-04-17 10:24 ` Aaron Carroll
2008-04-17 11:14 ` Fabio Checconi
2008-04-17 12:14 ` Aaron Carroll
2008-04-17 13:54 ` Jens Axboe
2008-04-17 15:18 ` Paolo Valente [this message]
2008-04-17 8:48 ` Pavel Machek
2008-04-17 8:57 ` Jens Axboe
2008-04-17 9:14 ` Fabio Checconi
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=48076A41.5040806@unimore.it \
--to=paolo.valente@unimore.it \
--cc=aaronc@cse.unsw.edu.au \
--cc=fchecconi@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.