Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1638173
| From | Jens Axboe <axboe@kernel.dk> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH BUGFIX] block, bfq: stress that low_latency must be off to get max throughput |
| Date | 2017-05-09 17:00 +0200 |
| Message-ID | <tFeMh-37Z-1@gated-at.bofh.it> (permalink) |
| References | <tFb22-AT-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 05/09/2017 04:54 AM, Paolo Valente wrote: > The introduction of the BFQ and Kyber I/O schedulers has triggered a > new wave of I/O benchmarks. Unfortunately, comments and discussions on > these benchmarks confirm that there is still little awareness that it > is very hard to achieve, at the same time, a low latency and a high > throughput. In particular, virtually all benchmarks measure > throughput, or throughput-related figures of merit, but, for BFQ, they > use the scheduler in its default configuration. This configuration is > geared, instead, toward a low latency. This is evidently a sign that > BFQ documentation is still too unclear on this important aspect. This > commit addresses this issue by stressing how BFQ configuration must be > (easily) changed if the only goal is maximum throughput. Added, thanks. -- Jens Axboe
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH BUGFIX] block, bfq: stress that low_latency must be off to get max throughput Paolo Valente <paolo.valente@linaro.org> - 2017-05-09 13:00 +0200 Re: [PATCH BUGFIX] block, bfq: stress that low_latency must be off to get max throughput Jens Axboe <axboe@kernel.dk> - 2017-05-09 17:00 +0200
csiph-web