Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH/RFC] qt4-embedded: tune QT_ARCH for armv6
Date: Sun, 07 Nov 2010 20:42:31 +0100	[thread overview]
Message-ID: <4CD70127.8060404@eukrea.com> (raw)
In-Reply-To: <4CD3DA8D.5020300@freyther.de>

Hi,

Le 05/11/2010 11:21, Holger Freyther a écrit :
> 1.) record a trace (e.g. the qtdemo) you will need Qt/X11 for that (desktop,
> device). But make sure that the qtdemo width/height fits on the screen.
>
> $ qttdemo -graphicssystem trace (exit the app normally)
>
> 2.) Use qttracereply to replay the trace, it will print nice FPS data.
>
>
here are the results :
Distro : angstrom-2010.x
CPU : i.MX357
Kernel : Linux 2.6.36+patches

trace generated using example concentriccirles (from qt4.7 X11 32bits sdk), 
screen resolution : 320x240 :
concentriccircles  -geometry 320x240  -graphicssystem trace

bench :
mount -o remount,ro /
qttracereplay ./qtgraphics-106954754.trace -qws (run 5 times)

=> qt4.7 with armv6 arch :
# qttracereplay ./qtgraphics-106954754.trace -qws
Read paint buffer version 1 with 282 frames
./qtgraphics-106954754.trace, iterations: 3, frames: 282, min(ms): 7403, 
median(ms): 7405, stddev: 0.012733 %, max(fps): 38.092665
./qtgraphics-106954754.trace, iterations: 3, frames: 282, min(ms): 7375, 
median(ms): 7376, stddev: 0.011070 %, max(fps): 38.237288
./qtgraphics-106954754.trace, iterations: 3, frames: 282, min(ms): 7370, 
median(ms): 7371, stddev: 0.016920 %, max(fps): 38.263229
./qtgraphics-106954754.trace, iterations: 3, frames: 282, min(ms): 7388, 
median(ms): 7389, stddev: 0.011050 %, max(fps): 38.170005
./qtgraphics-106954754.trace, iterations: 3, frames: 282, min(ms): 7372, 
median(ms): 7373, stddev: 0.016915 %, max(fps): 38.252849

=> qt4.7 with arm arch :
# qttracereplay ./qtgraphics-106954754.trace -qws
Read paint buffer version 1 with 282 frames
./qtgraphics-106954754.trace, iterations: 3, frames: 282, min(ms): 7435, 
median(ms): 7436, stddev: 0.010980 %, max(fps): 37.928716
./qtgraphics-106954754.trace, iterations: 3, frames: 282, min(ms): 7431, 
median(ms): 7434, stddev: 0.022866 %, max(fps): 37.949132
./qtgraphics-106954754.trace, iterations: 3, frames: 282, min(ms): 7456, 
median(ms): 7457, stddev: 0.010949 %, max(fps): 37.821888
./qtgraphics-106954754.trace, iterations: 3, frames: 282, min(ms): 7423, 
median(ms): 7424, stddev: 0.010998 %, max(fps): 37.990031
./qtgraphics-106954754.trace, iterations: 3, frames: 282, min(ms): 7417, 
median(ms): 7417, stddev: 0.050828 %, max(fps): 38.020763

Conclusion : no regression, nearly no improvement.

Eric



  parent reply	other threads:[~2010-11-07 19:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04  9:52 [PATCH/RFC] qt4-embedded: tune QT_ARCH for armv6 Eric Bénard
2010-11-04 18:05 ` Khem Raj
2010-11-04 18:26 ` Holger Freyther
2010-11-04 19:14   ` Eric Bénard
2010-11-05  9:32     ` Holger Freyther
2010-11-05  9:42       ` Eric Bénard
2010-11-05 10:21         ` Holger Freyther
2010-11-05 10:41           ` Eric Bénard
2010-11-07 19:42           ` Eric Bénard [this message]
2010-11-04 20:27   ` Khem Raj
2010-11-04 21:05   ` Koen Kooi
2010-11-05 11:21   ` Phil Blundell

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=4CD70127.8060404@eukrea.com \
    --to=eric@eukrea.com \
    --cc=openembedded-devel@lists.openembedded.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