From: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu-user-linux: how could I measure performance for aarch64 and arm?
Date: Thu, 10 Jan 2019 22:31:56 +0300 [thread overview]
Message-ID: <q186f8$1u3$1@blaine.gmane.org> (raw)
Hello,
I am running the same application compiled for aarch64 and armv7l on
x86_64 platform using qemu-user-linux tools.
I see dramatic performance difference (30 times) between emulated
architectures: aarch64 runs for ~4 minutes, armv7l runs for ~2 hours.
I do understand that CPU architecture emulation is inherently slow
thing, but my question is about the difference.
How could I debug to understand what is the reason for such a big
difference? I've already tried to run stress-ng compiled for this two
architectures, but it leads to the same performance per second.
I am running qemu 2.11, should I try other version?
next reply other threads:[~2019-01-10 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 19:31 Matwey V. Kornilov [this message]
2019-01-11 9:52 ` [Qemu-devel] qemu-user-linux: how could I measure performance for aarch64 and arm? Peter Maydell
2019-01-11 19:24 ` Matwey V. Kornilov
2019-01-13 7:31 ` Matwey V. Kornilov
2019-01-14 10:23 ` Peter Maydell
2019-01-14 10:30 ` Matwey V. Kornilov
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='q186f8$1u3$1@blaine.gmane.org' \
--to=matwey.kornilov@gmail.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).