public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Hao_Xu <[email protected]>, [email protected]
Subject: Re: [Question] testing results of support async buffered reads feature
Date: Sat, 10 Oct 2020 13:17:40 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 10/10/20 3:39 AM, Hao_Xu wrote:
> Hi Jens,
> I've done some testing for io_uring async buffered reads with fio. But I 
> found something strange to me.
> - when readahead is exactly turned off, the async buffered reads feature 
> appears to be worse than the io-wq method in terms of IOPS.
> - when readahead is on, async buffered reads works better but the 
> optimization rate seems to be related with the size of readahead.
> I'm wondering why.

I don't think these are necessarily unexpected. By and large, the async
buffered reads are faster, have lower latencies, and are a lot more
efficient in terms of CPU usage. But there are cases where the old
thread offload will be quicker, as you're essentially spreading the
copying over more cores and can get higher bandwidth that way.

If you're utilizing a single ring for your application, then there might
be gains to be had at the higher end of the IOPS or bandwidth spectrum
by selectively using IOSQE_ASYNC for a (small) subset of the issued
reads. 

-- 
Jens Axboe


      reply	other threads:[~2020-10-10 23:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10  9:39 [Question] testing results of support async buffered reads feature Hao_Xu
2020-10-10 19:17 ` Jens Axboe [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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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