Samsung took the wraps off a new Octa chip yesterday, the Exynos 5420, which brings higher clock speeds, a new and powerful GPU, and, all signs indicate, a fix to the bug that crippled the performance of the first Octa chip, Exynos 5410.
The Korean manufacturer highlighted in the press release the performance improvements that the new Exynos 5 Octa offers over the model that was first introduced in January, and especially the graphics prowess of the ARM Mali powered chip.
Folks at Engadget visited the SIGGRAPH 2013 trade show where they got the chance to compare a 10-inch reference tablet powered by the new Exynos 5420 chip with the Nexus 10, powered by a dual-core Exynos 5 Dual processor codenamed 5250. Both devices were set up to run the same benchmarks, and suffice to say you don’t have to be an expert to tell them apart. For the record, both devices have the same resolution of 2560 x 1600.
The benchmark used is the T-Rex test from the GLBenchmark 2.7.0 suite, which is designed to assess the graphical computation capabilities of mobile systems on a chip. The two competing GPUs are an ARM Mali T-628 in the case of the Octa and an ARM Mali T-604 in the case of the older Dual.
While it’s trivial that new tech is better than old tech, the Exynos 5 Dual is still a modern, highly-capable piece of silicon. The fact that the new Exynos 5 Octa outpaces it so categorically speaks volumes about the advancements in GPU tech that ARM and Samsung made over the past year. We look forward to see how the ARM Mali T-628 GPU does against the Imagination PowerVR SGX544MP3 GPU inside the first Exynos 5 Octa chip, the 5410.
Samsung says the Exynos 5420 is currently being sampled to clients and that mass manufacturing should begin in August. That means that mobile gamers will get to try out the first devices powered by new Exynos 5 Dual, including smartphones, tablets, and Chromebooks, starting this fall.
Like this post? Share it!
can it run crysis ;)
You had to ask.
Sorry , couldn’t stopped myself from asking :-) .
Yes, but only if its over clocked and watercooled
So that is what I needed to know. It’s 2X faster than nexus 10=> last gen exynos dual.
That means it is about as fast as prior octa with PowerVr 544 MP3 running at 533 MHz. And theoretically both of octa’s are still slower than iPad 4 GPU and adreno 330 in snapdragon 800.
Exynos 5 Dual has 25% faster GPU than first gen Octa (5410) and is twice slower than the new Octa (5420). And so T628MP6 GPU is around 2.5x faster than 544MP3 GPU.
Yes T628 is twice as fast as the T604.
Where you get that 544 result ? It’s one of the fastest GPU’s even today ! Something 2,5 times faster than PowerVr 544 MP3 at 533Mhz is about as fast as Intel HD graphics 3000 !
The SGX544 is a quite dated GPU already. Last gen from Imagination Tech is SGX554 (iPad 4), a much faster part.
from the benchmarks iv’e seen, the SGX554 in the iPad was just faster than the Adreno 320 in the S4 Pro and Snapdragon 600. So I would assume the t628 would be much better than that. meanwhile possibly matching the 330 in the Snapdragon 800
No. You must be confusing. Adreno 320 is more SGX543MP4 class (iPad 3 not the 4).
Don’t forget to compare the off screen performances if you’re looking to rank chips.
Until now, the SGX554 was the king of the hill. The first chip to overpower it is the Adreno 330.
Nope adreno 330 and mali t628 mp6 should go neck to neck while ipad 4 would lag behind ,btw ipad 5 may again come out as king
The Adreno 320 is about the same speed as the 554 in the iPad 4, and the 330 is faster than that. I would assume the T628 would be on par with the 330
different speed dual core CPU v’s different speed Quad core CPU ?
the CPU is still a metric that’s important in the rendering, from context switching to display lists, etc.
so unless they have same hardware, running at same speed, where the only difference is GPU’s, this is useless.
I wouldn’t say it “sailed through” considering it was still not smooth at all, but it was better :).
Come on, just stick a Titan in a tablet already! :DDD
What fps was it? On 5420 in glbebchmark? Pretty dumb not to state that.