From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Emilio G. Cota" <cota@braap.org>
Cc: "Richard Henderson" <rth@twiddle.net>,
"Laurent Vivier" <laurent@vivier.eu>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Benn�e" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Benchmarking linux-user performance
Date: Fri, 10 Mar 2017 11:45:33 +0000 [thread overview]
Message-ID: <20170310114531.GB2480@work-vm> (raw)
In-Reply-To: <20170310012339.GA7400@flamenco>
* Emilio G. Cota (cota@braap.org) wrote:
> Hi all,
>
> Inspired by SimBench[1], I have written a set of scripts ("DBT-bench")
> to easily obtain and plot performance numbers for linux-user.
>
> The (Perl) scripts are available here:
> https://github.com/cota/dbt-bench
> [ It's better to clone with --recursive because the benchmarks
> (NBench) are pulled as a submodule. ]
>
> I'm using NBench because (1) it's just a few files and they take
> very little time to run (~5min per QEMU version, if performance
> on the host machine is stable), (2) AFAICT its sources are in the
> public domain (whereas SPEC's sources cannot be redistributed),
> and (3) with NBench I get results similar to SPEC's.
Does NBench include anything with lots of small processes, or a large
chunk of code. Using benchmarks with small code tends to skew DBT optimisations
towards very heavy block optimisation that dont work in real applications where
the cost of translation can hurt if it's too high.
> Here are linux-user performance numbers from v1.0 to v2.8 (higher
> is better):
>
> x86_64 NBench Integer Performance
> Host: Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
>
> 36 +-+-+---+---+---+--+---+---+---+---+---+---+---+---+--+---+---+---+-+-+
> | + + + + + + + + + + + + + + + + *** |
> 34 +-+ #*A*+-+
> | *A* |
> 32 +-+ # +-+
> 30 +-+ # +-+
> | # |
> 28 +-+ # +-+
> | *A*#*A*#*A*#*A*#*A*# # |
> 26 +-+ *A*#*A*#***# *** ******#*A* +-+
> | # *A* *A* *** |
> 24 +-+ # +-+
> 22 +-+ # +-+
> | #*A**A* |
> 20 +-+ #*A* +-+
> | *A*#*A* + + + + + + + + + + + + + + + |
> 18 +-+-+---+---+---+--+---+---+---+---+---+---+---+---+--+---+---+---+-+-+
> v1.v1.1v1.2v1.v1.4v1.5v1.6v1.7v2.0v2.1v2.2v2.3v2.v2.5v2.6v2.7v2.8.0
> QEMU version
Nice, there was someone on list complaining about 2.6 being slower for them.
> x86_64 NBench Floating Point Performance
> Host: Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
>
> 1.88 +-+-+---+--+---+---+---+--+---+---+---+---+--+---+---+---+--+---+-+-+
> | + + + *A*#*A* + + + + + + + + + + + + |
> 1.86 +-+ *** *** +-+
> | # # *A*#*** |
> | *A*# # # ## *A* |
> 1.84 +-+ # *A* *A* # +-+
> | # # *A* |
> 1.82 +-+ # # ## +-+
> | # *A*# # |
> 1.8 +-+ # # #*A* *A* +-+
> | # *A* # # |
> 1.78 +-+*A* # *A* # +-+
> | # ***# # # |
> | *A*#*A* # # |
> 1.76 +-+ *** # # +-+
> | + + + + + + + + + + + + + + *A* + + |
> 1.74 +-+-+---+--+---+---+---+--+---+---+---+---+--+---+---+---+--+---+-+-+
> v1.v1.v1.2v1.3v1.4v1.v1.6v1.7v2.0v2.1v2.v2.3v2.4v2.5v2.v2.7v2.8.0
> QEMU version
I'm assuming the dips are where QEMU fixed something and cared about corner
cases/accuracy?
Dave
> Same plots, in PNG: http://imgur.com/a/nF7Ls
>
> These plots are obtained simply by running
> $ QEMU_PATH=path/to/qemu QEMU_ARCH=x86_64 make -j
> from dbt-bench, although note that some user intervention was needed
> to compile old QEMU versions.
>
> I think having some well-defined, easy-to-run benchmarks (even
> if far from perfect, like these) to aid development is better
> than not having any. My hope is that having these will encourage
> future performance improvements to the emulation loop and TCG -- or
> at least serve as a warning when performance regresses excessively :-)
>
> Let me know if you find this work useful.
>
> Thanks,
>
> Emilio
>
> [1] https://bitbucket.org/simbench/simbench
> Simbench's authors have a paper on it, although it is not publicly
> available yet (will be presented at the ISPASS'17 conference in April).
> The abstract can be accessed here though: http://tinyurl.com/hahb4yj
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-03-10 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 1:23 [Qemu-devel] Benchmarking linux-user performance Emilio G. Cota
2017-03-10 11:45 ` Dr. David Alan Gilbert [this message]
2017-03-10 11:48 ` Peter Maydell
2017-03-11 2:25 ` Emilio G. Cota
2017-03-11 15:02 ` Peter Maydell
2017-03-11 2:18 ` Emilio G. Cota
2017-03-14 17:06 ` Dr. David Alan Gilbert
2017-03-16 17:13 ` Emilio G. Cota
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=20170310114531.GB2480@work-vm \
--to=dgilbert@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).