Project Home
Project Home		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Graphics/Discussion/OpenGL ES/Performace on i.MX53 using OpenGL ES 1.1/List of Posts
Forum Topic - Performace on i.MX53 using OpenGL ES 1.1: (4 Items)
   
Update
Howard Smith(deleted)
11/12/2010 12:37 PM
post74494
Performace on i.MX53 using OpenGL ES 1.1   
Hello,

I have been doing some benchmarking on gles1-egl demos such as gles1-egl-coaster, planetary, gears etc and have found 
very poor performace on i.MX53 running QNX 6.5.0 with arm v7 instructions and gcc 4.4.2.  quite a few of them run sub 10
 FPS and this one, gles1-egl-gears hits about 33 FPS.  The openGL ES 2.0 version, gles2-egl-gears runs at 199 FPS.  I 
would expect the openGL ES 1.1 demo to run much faster than 33 FPS on this hardware. 

 I did a pidin -p and got the following which seems to indicated I am running with HW acceleration not SW but I'm not 
sure.

 pidin -P gles1-egl-gears mem
     pid tid name               prio STATE            code  data        stack
  176141   1 gles1-egl-gears     10r READY             20K   19M   24K(516K)*
            libc.so.3          @ 1000000             460K   16K
            libGLESv1_CM.so.1  @78000000              20K  4096
            libEGL.so.1        @78006000              36K  8192
            libgsl_iMX5X.so.1  @78011000              32K  4096
            libiow.so.1        @7801a000              20K  4096
            libm.so.2          @78020000             148K  8192
            libc2d_iMX5X.so.1  @78047000              48K  8192
            libEGL_iMX5X.so    @78060000              72K  4096
            devg-imx51.so      @78073000              40K  8192
            libgf.so.1         @78080000              96K  4096
            libffb.so.2        @780a0000             148K  8192
            libcpp.so.4        @780d0000             328K   36K
            GLESv1_CM_iMX5X.so @78130000             204K  8192
            libGLESv2_iMX5X.so @78200000            2756K   80K
            em/ctl-0000,0000,0 @28000000 (       0)        4096
            mem/rbSharedMemory @28001000 (       0)        4096
            face-0000,0000,0:1 @28010000 (       0)        752K
            face-0000,0000,0:0 @280d0000 (       0)        752K
            /dev/mem           @28200000 (       0)         16M
# 164 frames in  5.017 seconds = 32.689 FPS  

Are there any tricks to get OpenGL ES 1.1 to run properly.  We see the same performace issues on i.MX51.

Thanks,

Howie
John Edwards
09/14/2011 6:12 PM
post88832
Re: Performace on i.MX53 using OpenGL ES 1.1   
I have been experimenting with the i.MX53 QSB and successfully have OpenGL ES 1.1, OpenGL ES 2.0, and OpenVG demo 
applications running.  However, I am also seeing drastic performance discrepancies with what the i.MX53 should be 
capable of rendering.

gles2-egl-gears:
OpenGL ES 2.0 seems to perform the best currently being limited to vsync @ 60 fps and only using around 28% CPU as 
reported by top.

gles1-egl-gears:
OpenGL ES 1.1 is much worse providing 30 fps and using around 60% of the CPU.

vg-egl-tiger:
OpenVG is much worse than the others running at 15 fps and using around 85% to 90% of the CPU.  This is basically 
unusable and difficult to imagine the GPU2D module is producing performance that low.  That's worse performance than the
 i.MX35 processor that uses the same GPU2D module at a lower clock speed.

Are there any known issues regarding accelerated graphics performance on the i.MX53?  Does QNX plan to improve these 
levels of performance?  Any information would be very helpful in this matter.

Sincerely,
John
Jason Mawdsley
09/14/2011 9:00 PM
post88835
Re: Performace on i.MX53 using OpenGL ES 1.1   
You are running swap interval 1, you cannot run benchmarks with swap
interval 1.

Remember, with swap interval 1, the following applies:
Rendering at > 60 fps means you are capped at 60fps
Rendering between 30-59fps means you are capped at 30 fps
Rendering between 20-29 fps means you are capped at 20 fps
Rendering between 15fps and 19 fps means you are capped at 15 fps

Etc


What performance did you get on Tiger on the imx35?

Jason

On 11-09-14 6:12 PM, "John Edwards" <community-noreply@qnx.com> wrote:

>I have been experimenting with the i.MX53 QSB and successfully have
>OpenGL ES 1.1, OpenGL ES 2.0, and OpenVG demo applications running.
>However, I am also seeing drastic performance discrepancies with what the
>i.MX53 should be capable of rendering.
>
>gles2-egl-gears:
>OpenGL ES 2.0 seems to perform the best currently being limited to vsync
>@ 60 fps and only using around 28% CPU as reported by top.
>
>gles1-egl-gears:
>OpenGL ES 1.1 is much worse providing 30 fps and using around 60% of the
>CPU.
>
>vg-egl-tiger:
>OpenVG is much worse than the others running at 15 fps and using around
>85% to 90% of the CPU.  This is basically unusable and difficult to
>imagine the GPU2D module is producing performance that low.  That's worse
>performance than the i.MX35 processor that uses the same GPU2D module at
>a lower clock speed.
>
>Are there any known issues regarding accelerated graphics performance on
>the i.MX53?  Does QNX plan to improve these levels of performance?  Any
>information would be very helpful in this matter.
>
>Sincerely,
>John
>
>
>
>_______________________________________________
>
>OpenGL ES
>http://community.qnx.com/sf/go/post88832
>
John Edwards
09/14/2011 10:05 PM
post88836
Re: Performace on i.MX53 using OpenGL ES 1.1   
Thanks for the reply.  You are correct, I forgot about swap interval set to 1.  Tomorrow I will re-run the benchmarks 
with it set to 0 to see if there is any difference.

What concerns me more than the FPS achieved is the amount of CPU being used by the demos.  It seems abnormally elevated 
for this part (almost high enough to seem using a software rendered fallback or something).  Especially the 90% in the 
OpenVG demo.

I will also try running the OpenVG tiger demo on the i.MX35 tomorrow to see what the performance characteristics are 
with FPS and CPU load.

Again, thanks for the reply.  I would definitely like to keep following up on this issue, as hardware accelerated 
graphics (especially of the OpenVG variant) are imperative for our current application.

--john

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems