POV-Ray : Newsgroups : povray.general : Povray 3.7 on various ARM devices Server Time
29 Dec 2024 13:20:55 EST (-0500)
  Povray 3.7 on various ARM devices (Message 1 to 1 of 1)  
From: jhu
Subject: Povray 3.7 on various ARM devices
Date: 8 Dec 2013 02:20:01
Message: <web.52a41cd8ec0fd7b8d19b0ec40@news.povray.org>
Samsung Chromebook (Exynos 5250 @ 1.7 GHz, dual-core ARM Cortex A15)
Ubuntu 12.04 in a ChromeOS chroot
gcc 4.6, -mcpu=cortex-a9 -mtune=cortex-a9
  (132.52 pps, 77.95 pps/GHz, 66.26 pps/core, 38.97 pps/core/GHz)

  Photon Time:      0 hours  0 minutes  8 seconds (8.361 seconds)
              using 5 thread(s) with 9.617 CPU-seconds total
  Radiosity Time:   No radiosity
  Trace Time:       0 hours 32 minutes 58 seconds (1978.105 seconds)
              using 2 thread(s) with 3924.586 CPU-seconds total

gcc 4.6, -mcpu=cortex-a15 -mtune=cortex-a15
  (126.37 pps, 74.34 pps/GHz, 63.19 pps/core, 37.17 pps/core/GHz)

Render Time:
  Photon Time:      0 hours  0 minutes  8 seconds (8.294 seconds)
              using 5 thread(s) with 9.491 CPU-seconds total
  Radiosity Time:   No radiosity
  Trace Time:       0 hours 34 minutes 34 seconds (2074.371 seconds)
              using 2 thread(s) with 4114.285 CPU-seconds total
*************************************************************************
Google/LG Nexus 4 (Qualcomm S4 Pro APQ8064 @ 1.5 GHz, quad core Krait 200)
Debian 7 in a chroot
  gcc 4.6, -mcpu=cortex-a9 -mtune=cortex-a9
  (110.76 pps, 73.84 pps/GHz, 27.69 pps/core, 18.46 pps/core/GHz)

  Photon Time:      0 hours  0 minutes 15 seconds (15.944 seconds)
              using 7 thread(s) with 17.526 CPU-seconds total
  Radiosity Time:   No radiosity
  Trace Time:       0 hours 39 minutes 26 seconds (2366.788 seconds)
              using 4 thread(s) with 9271.972 CPU-seconds total
*************************************************************************
Samsung Galaxy S II(Exynos 4210 @ 1.2 GHz, dual core ARM Cortex A9)
Debian 7 in a chroot
  (48.15 pps, 40.12 pps/GHz, 24.08 pps/core, 20.06 pps/core/GHz)

  Photon Time:      0 hours  0 minutes 21 seconds (21.621 seconds)
              using 5 thread(s) with 21.926 CPU-seconds total
  Radiosity Time:   No radiosity
  Trace Time:       1 hours 30 minutes 44 seconds (5444.819 seconds)
              using 2 thread(s) with 9947.091 CPU-seconds total
*************************************************************************
Barnes & Noble Nook Tablet (TI OMAP4430 @ 1.0 GHz, dual core ARM Cortex A9)
Debian 7 in a chroot
  (53.66 pps, 53.66 pps/GHz, 26.83 pps/core, 26.83 pps/core/GHz)

  Photon Time:      0 hours  0 minutes 20 seconds (20.210 seconds)
              using 5 thread(s) with 22.850 CPU-seconds total
  Radiosity Time:   No radiosity
  Trace Time:       1 hours 21 minutes 25 seconds (4885.504 seconds)
              using 2 thread(s) with 9677.514 CPU-seconds total

For comparison
Phenom II x6, 1090T (6 cores @ 3.2 GHz, turbo 3.6 GHz),
FreeBSD 9.0, gcc 4.6, -march=barcelona
  (1388.11 pps, 385.58 pps/GHz, 231.35 pps/core, 64.26 pps/core/GHz)

Render Time:
  Photon Time:      0 hours  0 minutes  2 seconds (2.144 seconds)
              using 9 thread(s) with 2.483 CPU-seconds total
  Radiosity Time:   No radiosity
  Trace Time:       0 hours  3 minutes  8 seconds (188.850 seconds)
              using 6 thread(s) with 1129.224 CPU-seconds total


What's interesting is that the the SGS II and B&N Nook Tablet both have Cortex
A9 CPUs, but the Nook Tablet finishes faster despite being at a lower
clockspeed. OTOH, the SGS II has a better GPU, so Android performance is much
better on the SGS 2. Also Krait 200 has a lower per core performance than Cortex
A9. But again, Android performance is not diminished noticeably (if at all) on
my Nexus 4, probably due to the better GPU.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.