Why you can trust Tom's Hardware Our expert reviewers spend hours testing and comparing products and services so you can choose the best for you. Find out more about how we test.
GPU And Gaming Performance
Mobile GPU performance is becoming increasingly important as people begin to see their phones and tablets as portable gaming machines. This section explores GPU performance with several synthetic and real-world game engine tests. To learn more about how these benchmarks work, what versions we use, or our testing methodology, please read our article about how we test mobile device GPU performance.
It is no surprise that the Moto E outperforms the Moto G in the CPU-bound Physics test by 16%, but it is surprising to see the Adreno 305 in the Moto G ahead of the newer Adreno 306 in the Moto E. While Qualcomm’s Adreno GPUs are something of a black box, based on the product numbering it is reasonable to suspect the 306 is just a slightly tweaked 305, with maybe a few performance optimizations. There is one big difference between two, one that can potentially explain intuitively reversed results: clock frequency. The Adreno 305 in the Moto G (2nd gen) runs at up to 450MHz, while the Adreno 306 in the Moto E (2nd Gen) runs at up to 400MHz. Not taking into account any architectural changes, or the fact that performance never scales perfectly with frequency, this is a 12.5% advantage for the Moto G.
The Moto E is definitely not a gaming powerhouse, trailing the Desire Eye by a factor of 5.5x overall. Compared to the Moto G, we see about a 12% deficit that’s consistent between Dunes and Hangar, equaling the GPU clock frequency spread between the two.
The Lumia 830 manages to squeeze past the Moto G in both graphics tests despite using the same Snapdragon 400 SoC. Since the benchmark uses Direct3D feature level 9_3 when running on Windows instead of OpenGL ES 2.0 for Android, the small difference could be due to the graphics API overhead.
In the onscreen tests, the Moto E pulls ahead because it renders at a lower 960x540 resolution versus the Moto G’s 1280x720.
The performance gap between the Adreno 306 and the Adreno 330 remains the same when moving to the high quality tests. However, we see the Moto E swap places with the Moto G. This is likely a combination of the Moto E’s higher memory bandwidth and better CPU performance.
The Lumia 830 could not run the high quality tests because of insufficient memory.
Both of the Moto devices choke on the pixel shader heavy GFXBench Manhattan test. They still fare better than the Lumia 830, which refused to run it at all.
Once again we see a 12% deficit between the Moto E and Moto G, although neither perform well.
In GFXBench 3.0 Alpha Blending, the Moto E (2nd gen) falls behind the Moto G by a wider 28% margin in this test of texturing capability. This test is usually memory bandwidth sensitive, so it is odd that the Snapdragon 410 does so poorly here. Granted, it is still 3x faster than the Lumia 830.
The ALU test stresses fragment shader computing. Here we see the familiar -12.5% delta between the Moto E and Moto G. Nearly the same delta shows up again in the Driver Overhead test.
By now it should be clear that neither the Adreno 305 or 306 are capable of playing the most demanding Android games. Fortunately, most mobile games are not nearly as demanding as the graphics benchmarks we use. The lower screen resolution of the Moto E (2nd gen) also helps it outperform the the Moto G in onscreen tests, and it is still capable of handling some casual gaming.
The Moto G (2nd gen) maintains about a 12.5% advantage over the Moto E (2nd gen) in graphics performance at the same resolution, the exact same difference in GPU clock frequency between the two. It’s unfortunate that the Adreno 306 in Snapdragon 410 is slower than the Adreno 305 in the older Snapdragon 400 head-to-head. I suspect the lower GPU clock for the 306 is a result of squeezing the A53 CPU cores, which have a lower performance per watt than the A7 cores, into the same power envelope.
