All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] chroot to ARM Gentoo install.
Date: Fri, 27 Aug 2004 00:48:27 +0100	[thread overview]
Message-ID: <200408270048.27414.paul@codesourcery.com> (raw)
In-Reply-To: <412D147D.3020803@bellard.org>

On Wednesday 25 August 2004 23:36, Fabrice Bellard wrote:
> I am curious to know what speed you get in user mode emulation.

I did some benchmarking on on a 2GHz amd64 machine running in 32-bit mode.
I don't have a real arm machine for comparison. 

I did two runs. One native (i486), the other soft-float armv4 using qemu. 

First I ran the SPECint benchmarks. These mainly stress integer CPU and memory 
performance. I'm not sure if I'm allowed to give actual results, so I'll just 
give a summary for now.

Five tests fail to execute properly. I haven't tried the executables on real 
arm hardware, so these may be compiler/libc bugs.

One test runs a mere 60% slower. The other six tests take between 3 and 7 
times as long to run.

I also ran the bonnie++ disk IO benchmark. The machine was under intermittent 
light load while the tests were run, so there's probably some variation in 
the numbers.

Native:
 1.03       ------Sequential Output------ --Sequential Input- --Random-
            -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
       Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
         4G 30667  75 31279  12 14788   5 21951  60 34922   5 161.0   0
            ------Sequential Create------ --------Random Create--------
            -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
      files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
         16  2296  98 +++++ +++ +++++ +++  2267  97 +++++ +++ 10236  99

qemu-arm:
 1.03       ------Sequential Output------ --Sequential Input- --Random-
            -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
       Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
         4G     0   0 31734  10     0   0 +++++ +++ 36888   5 167.8   0
            ------Sequential Create------ --------Random Create--------
            -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
      files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
         16  2733  97 +++++ +++ +++++ +++  2863  98 +++++ +++  9947  93

Strangely the qemu results are showing zero for per-char IO. I guess this is a 
bug somewhere. The per-char write results should be ~6000K/s

Paul

  reply	other threads:[~2004-08-26 23:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 19:38 [Qemu-devel] chroot to ARM Gentoo install James Pellow
2004-08-24 20:06 ` Paul Brook
2004-08-24 21:26   ` Lennert Buytenhek
2004-08-24 21:44     ` Paul Brook
2004-08-24 22:14       ` Fabrice Bellard
2004-08-24 22:26         ` Paul Brook
2004-08-25 22:36           ` Fabrice Bellard
2004-08-26 23:48             ` Paul Brook [this message]
2004-12-18 21:18       ` Lennert Buytenhek
2004-08-24 22:44   ` James Pellow
2004-08-24 22:44     ` Paul Brook

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=200408270048.27414.paul@codesourcery.com \
    --to=paul@codesourcery.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 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.