Personal computing discussed
Moderators: renee, David, mac_h8r1, Nelliesboo
derFunkenstein wrote:Samsung Vibrant (Hummingbird Cortex A8) - 205
Nexus 7 -
1 thread - 197
2 thread - 526
4 thread - 920
chuckula wrote:Thanks for the update! It now runs on my CM7-hacked Motorola Triumph, which is very low-end compared to most phones on this thread:
Using version 1.2:
1. 1 Thread: 960 MFlops (this is a single-core CPU)
2. 2 Threads: 400 MFlops
3. 4 Threads: 381 MFlops
codedivine wrote:chuckula wrote:Thanks for the update! It now runs on my CM7-hacked Motorola Triumph, which is very low-end compared to most phones on this thread:
Using version 1.2:
1. 1 Thread: 960 MFlops (this is a single-core CPU)
2. 2 Threads: 400 MFlops
3. 4 Threads: 381 MFlops
960 MFlops on a single-core Snapdragon S2
Not what I was expecting. I would have expected more like 400 MFlops or so. Are you sure that is not a typo?
chuckula wrote:The first results I submitted were what the phone displayed, but I just ran the benchmark again and I got different results. I changed my settings so that the phone does not turn off the screen or go to sleep during the benchmark run. This is a CM-7 phone with Android 2.3.7, but the CPU is not overclocked (1 GHz base clock).
Here's another run using 1 thread: 335 MFlops.
So there ya go.. sometimes there might be an outlier sneaking into the mix
codedivine wrote:Clearly, Krait is showing a much higher performance than either Qualcomm S3 or the ARM Cortex A9
codedivine wrote:Now live in Google Play: https://play.google.com/store/apps/deta ... ne.rgbench
codedivine wrote:For everyone's benefit, scores collected from other users :
1. Nexus 7 : 1470 MFlops
2. Galaxy S2 (international, Exynos 4410): 890 MFlops
3. Galaxy S2X (T-mobile, Snapdragon S3): 1040 MFlops
4. Transformer TF201 (Tegra 3, 1.3GHz): 1881 MFlops
5. Galaxy S3 (international Exynos 4 Quad): 2189 Mflops
codedivine wrote:From a user with a Snapdragon S4 based HTC One X:
Single thread: 730 MFlops
Two threads: 1460 MFlops
derFunkenstein wrote:codedivine wrote:Now live in Google Play: https://play.google.com/store/apps/deta ... ne.rgbench
I pushed it to my Nexus 7 and my wife's Acer Tegra 2 tablet and I'll just verify that I see similar performance when I get home.
DancinJack wrote:
TI OMAP 4460 Scores: Underclocked to 1GHz from 1.2GHz
Single thread: 295.0 MFlops
Two threads: 778.0 MFlops
codedivine wrote:You will see *slightly* different performance. Unfortunately, even in v1.2 there was a bug. (I wanted to die of shame, again, but here I am still alive )
However, everything looks good now.
codedivine wrote:This is from the Play version ?
ChronoReverse wrote:I like that it has a progress indicator now.
It would be good to disable the onscreen controls (the dropdown list and the Run button) until a test it complete though.
Also, it should be possible to keep the screen from sleeping while the benchmark is actively running.
Galaxy Note, Snapdragon S3 @ 1.5GHz, running Android 4.1 (JB, CM10), RgbenchMM 1.3
2 threads: 1153 MFlops
1 thread: 572 MFlops
DancinJack wrote:The lowly OMAP in my Nexus weeps. At least I get updates and stock Android?
codedivine wrote:Thanks for the suggestions. Now that the benchmark actually works, I can look into doing this.
ChronoReverse wrote:Hmm, considering it's an A9 chip that should have higher per clock performance than the Snapdragon S3 (I'd say at least 10%), the settings for your CPU are hindering its performance significantly. I suspect the undervolting might be too aggressive for instance. The low single thread scores also indicate an overly aggressive governor.
ChronoReverse wrote:I like that it has a progress indicator now.
It would be good to disable the onscreen controls (the dropdown list and the Run button) until the test is completed. Either that or use wakelock to keep the CPU from entering sleep state.
Also, it should be possible to keep the screen from sleeping while the benchmark is actively running.
derFunkenstein wrote:I got 1.3.1 on my Nexus 7 and my wife's A100.
The Nexus 7 results aren't really any different. I got 292 1 thread and 1488 4 thread.
The Acer A100 (Tegra 2) got 296 1 thread and 714 for 2
Still weird to see the huge 1-thread drop-off, but the results are consistent.