The CPU clocks never drop below that, even when just sitting idle at the menu screen of the benchmark. Firing up GLBenchmark 2.5.1 causes a switch to the ARM Cortex A15 cluster, with a default frequency of 1.2GHz. Using System Monitor I kept an eye on CPU frequency while running the same tests. The original post on B3D focused on GPU performance, but I was curious to see if CPU performance responded similarly to these benchmarks. The reason for the difference? GLBenchmark 2.5.1 appears to be singled out as a benchmark that is allowed to run the GPU at the higher frequency/voltage setting. We should see roughly an 11% increase in performance in GLBenchmark 2.5.1 over GFXBench 2.7.0, and we end up seeing a bit more than that.
The results of the triangle throughput test offer additional confirmation for the frequency difference: We confirmed with Kishonti, the makers of the benchmark, that the low level tests are identical between the two benchmarks. Interestingly enough, GFXBench 2.7.0 (formerly GLBenchmark 2.7.0) is unaffected. The same is true for AnTuTu and Quadrant. Samsung never publicly claimed max GPU frequencies for the Exynos 5 Octa (our information came from internal sources), so no harm no foul thus far.įiring up GLBenchmark 2.5.1 however triggers a GPU clock not available elsewhere: 532MHz. Running any games, even the most demanding titles, returned a GPU frequency of 480MHz - just like alleged. Running that command in a loop we can get real time updates on the GPU frequency while applications run different workloads. Let’s hope this doesn’t get plugged, because it’s actually an extremely useful level of transparency that I wish more mobile platform vendors would offer. Simply run the following command over adb and it’ll return the current GPU frequency in MHz:Īdb shell cat /sys/module/pvrsrvkm/parameters/sgx_gpu_clk Samsung awesomely exposes the current GPU clock without requiring root access. For the past few weeks we’ve been asked by many to look into this, what follows are our findings. Through some good old fashioned benchmarking, the poster alleged that Samsung was only exposing its 533MHz GPU clock to certain benchmarks - all other apps/games were limited to 480MHz. More recently, a post over at Beyond3D from gave us reason to dust off our international SGS4s. As always, the insane pace of mobile got in the way and we both got pulled into other things. We both had plans to do a deeper dive into the power and performance characteristics of one of the first major smartphone platforms to use ARM’s Cortex A15. GPU duties are handled by a PowerVR SGX 544MP3, capable of running at up to 533MHz. Both of these came from Negri Electronics, a mobile device importer in the US.įor those of you who aren’t familiar with the Exynos 5 Octa in these devices, the SoC integrates four ARM Cortex A15 cores (1.6GHz) and four ARM Cortex A7 cores (1.2GHz) in a big.LITTLE configuration. Anand bought an international model GT-I9500 while I held out for the much cooler SK Telecom Korean model SHV-E300S, including Samsung’s own SS222 LTE modem capable of working on band 17 (AT&T LTE) and Band 2,5 WCDMA in the US. Somehow both Anand and I ended up with international versions of Samsung’s Galaxy S 4, equipped with the first generation Exynos 5 Octa (5410) SoC.
0 kommentar(er)
