public inbox for [email protected]
 help / color / mirror / Atom feed
From: Dmitry Sychov <[email protected]>
To: io-uring <[email protected]>
Subject: How good single uring scales across multiple cpu cores
Date: Thu, 4 Jun 2020 05:17:39 +0300	[thread overview]
Message-ID: <CADPKF+cKmLBy-71e+KUEq8k4fEF=bpVVrKiO84SL26de=9f+xg@mail.gmail.com> (raw)

Hey,

With the intro of uring there is finally a sane aio interface which
allows straight porting of Win IOCP-based apps to Linux - hooray.

The question though which I've raised in the prev. thread but was
kinda unanswered is how good
single uring submits+retrieves are at scaling across multiple active
user threads for socket io, still bound(to prevent excessive ctx
switches) by the overall number of system cores.

For IOCP I'am observing raw socket TPS increase with every added core
thread up to like 32..64 of them using single submit+completion queue
pair.

All uring benchmarks I've found lack specific context like the number
of running threads and there is no data on the gains from multicore
submits/retrieves against a single uring that make them kinda not to
the point...

Dmitry

                 reply	other threads:[~2020-06-04  2:18 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='CADPKF+cKmLBy-71e+KUEq8k4fEF=bpVVrKiO84SL26de=9f+xg@mail.gmail.com' \
    [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