From: Emilio Cota <cota@braap.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 2/2] tcg: use QTree instead of GTree
Date: Sun, 29 Jan 2023 17:32:05 -0500 [thread overview]
Message-ID: <Y9bz5QMpZAhGP6DR@cota-l14> (raw)
In-Reply-To: <Y76nTaoek2kVtLqJ@redhat.com>
On Wed, Jan 11, 2023 at 12:10:53 +0000, Daniel P. Berrangé wrote:
> On Tue, Jan 10, 2023 at 10:55:36PM -0500, Emilio Cota wrote:
> > Performance impact on linux-user:
> > - ~2% slowdown in spec06
> > - 1.05% slowdown in Nbench-int
> > - 4.51% slowdown in Nbench-fp
>
> What do you get *before* applying this patch, if you just run
> linux-user with G_SLICE=always-malloc set ?
>
> Also what libc impl were you testing with ? glibc or musl or something
> else ?
I've now done a few runs of nbench and the measurements I'm getting
are within noise. So I'd say no perf difference.
For SPEC I don't have time right now although I could do more runs
if you think they're needed.
I'm tempted for v2 to just remove these macrobenchmark numbers, since
with perf we can see that little time is spent on gtree anyway,
and at the moment I don't have time to do proper benchmarking.
Thanks,
E.
next prev parent reply other threads:[~2023-01-29 22:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 3:55 [PATCH 0/2] fix for #285 Emilio Cota
2023-01-11 3:55 ` [PATCH 1/2] util: import GTree as QTree Emilio Cota
2023-01-11 12:08 ` Daniel P. Berrangé
2023-01-29 22:28 ` Emilio Cota
2023-01-11 3:55 ` [PATCH 2/2] tcg: use QTree instead of GTree Emilio Cota
2023-01-11 12:10 ` Daniel P. Berrangé
2023-01-29 22:32 ` Emilio Cota [this message]
2023-01-11 12:34 ` Daniel P. Berrangé
2023-01-25 15:58 ` Daniel P. Berrangé
2023-01-29 22:38 ` Emilio Cota
2023-01-30 9:27 ` Daniel P. Berrangé
2023-01-30 19:09 ` Richard Henderson
2023-02-05 16:41 ` Emilio Cota
2023-01-11 12:26 ` [PATCH 0/2] fix for #285 Daniel P. Berrangé
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=Y9bz5QMpZAhGP6DR@cota-l14 \
--to=cota@braap.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.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 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).