From: Antti P Miettinen <ananaza@iki.fi>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] emulated ARM performance vs real processor ?
Date: Sun, 04 Sep 2011 20:42:10 +0300 [thread overview]
Message-ID: <8762l8cih9.fsf@iki.fi> (raw)
In-Reply-To: CAL_2VdCbmoArVcYsgoRRq5mO2s=9Q1D9JJnOESgBpE6vKF1YsA@mail.gmail.com
Julien Heyman <bidsomail@gmail.com> writes:
> Hi,
>
> I was wondering if anyone had some data regarding the relative performance of
> any given ARM board emulated in QEMU versus the real thing. Yes, I do know
> this depends a lot on the host PC running qemu, but some ballpark/example
> figures would help. Say, I emulate a 400 Mhz ARM9 processor on a Core2Duo
> laptop @ 2 Ghz, what kind of performance/timing ratio should I expect, one way
> or the other ? For example, for boot time.
> I have no idea whether the overhead of emulation is over-compensated by the
> huge processing power of the host compared to the real HW target, and by which
> factor.
>
> Regards,
> Julien
>
Taking a look at:
http://adt.cs.upb.de/quf/quf2011_proceedings.pdf
page 20 (24th page in the PDF), figure 1b, the noprof bars, I'd expect
2GHz host to be on average faster than native target. The emulation
speed depends on how core intensive vs memory intensive your workload
is. Workloads that are memory bound in the target (e.g. gzip ASCII
compression) can me emulated much faster (e.g. factor of two) than core
bound workloads (e.g. mcrypt encryption).
--
http://www.iki.fi/~ananaza/
next prev parent reply other threads:[~2011-09-04 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 7:32 [Qemu-devel] emulated ARM performance vs real processor ? Julien Heyman
2011-09-02 14:31 ` David Gilbert
2011-09-02 16:04 ` Julien Heyman
2011-09-02 16:10 ` David Gilbert
2011-09-02 16:56 ` M P
2011-09-04 17:42 ` Antti P Miettinen [this message]
2011-09-04 18:44 ` Peter Maydell
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=8762l8cih9.fsf@iki.fi \
--to=ananaza@iki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.