From: Vasily Tarasov <vtaras@sw.ru>
To: axboe@suse.de
Cc: linux-kernel@vger.kernel.org, Kirill Korotaev <dev@sw.ru>
Subject: ioprio feature behaviour
Date: Thu, 25 May 2006 14:56:57 +0400 [thread overview]
Message-ID: <44758D79.3020302@sw.ru> (raw)
Hello.
I produced a little test of ioprio feature. Results are basically good
enough,
but there is something strange on my mind.
The test just runs 8 simple readers with priorities 0, 1, .., 7 in best
effort class.
Readers read from files and count how much Mbytes per second they can read.
Results are here:
Process # (prio) Measurement 1 (Mbps) Measurement 2 (Mbps)
Measurement 3 (Mbps)
0 6,60
7,37 6,19
1 7,87
7,90 7,15
2 5,92
4,75 4,61
3 3,31
3,34 3,4
4 0,95
0,97 1,03
5 1,14
1,23 1,2
6 0,83
0,96 0,83
7 0,41
0,41 0,41
( The whole results are at http://www.7ka.mipt.ru/~vass/cfq-tests/tests.pdf)
The questions are:
1) Why process 0 with priority 0 has less bandwidth than process 1 with
priority 1?
2) The same with processes (priorities) 4, 5?
3) Why there is no _uniform_ dependence between bandwidth and priority?
4) Why sums of bandwidths of processes when priorities are setted and
when they are not setted (look in pdf) aren't equal?
Thanks, Vasily.
reply other threads:[~2006-05-25 12:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44758D79.3020302@sw.ru \
--to=vtaras@sw.ru \
--cc=axboe@suse.de \
--cc=dev@sw.ru \
--cc=linux-kernel@vger.kernel.org \
/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.