From: Kevin Wolf <kwolf@redhat.com>
To: "Lukáš Doktor" <ldoktor@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Performance improvement with 81f730d4
Date: Wed, 19 Apr 2023 10:16:19 +0200 [thread overview]
Message-ID: <ZD+jU35n+6xwNY/H@redhat.com> (raw)
In-Reply-To: <f8f0c9ff-5cb9-a440-f84f-19d55f7036a8@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
Hi Lukáš,
Am 19.04.2023 um 08:02 hat Lukáš Doktor geschrieben:
> Hello Paolo,
>
> the perf-ci detected and bisected the 81f730d4 - block, block-backend:
> write some hot coroutine wrappers by hand - as a performance
> improvement with 4K read/writes across various profiles. Without
> pinning it was about 10%, with pinned qemu about 15%.
>
> https://ldoktor.github.io/tmp/RedHat-virtlab722/v8.0.0/130-improvement.html
I must admit that I don't really understand how to read this page, and
which build corresponds to which QEMU revision (or even which one is
older and which one is newer).
All the build names are links, but they only result in a 404.
> Based on the commit message I guess it's expected, so my question is
> whether I should report such obvious improvements or only report
> improvements/regressions that are not that obvious?
I think it's useful to know that we did indeed fix the performance
problem, so as far as I am concerned, please do report them.
When we're addressing a regression, the most interesting part would of
course be comparing to the version before the regression was introduced
(pre-d8fbf9aa85a in this case) to see if the regression was fully fixed.
Maybe the page you linked above does already explain this and I just
don't know where to look? :-)
Kevin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-19 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 6:02 Performance improvement with 81f730d4 Lukáš Doktor
2023-04-19 8:16 ` Kevin Wolf [this message]
2023-04-19 13:01 ` Lukáš Doktor
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=ZD+jU35n+6xwNY/H@redhat.com \
--to=kwolf@redhat.com \
--cc=ldoktor@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).