NVIDIA's Tegra 3 Launched: Architecture Revealed
by Anand Lal Shimpi on November 9, 2011 12:34 AM ESTThe Tegra 3 GPU: 2x Pixel Shader Hardware of Tegra 2
Tegra 3's GPU is very much an evolution of what we saw in Tegra 2. The GeForce in Tegra 2 featured four pixel shader units and four vertex shader units; in Tegra 3 the number of pixel shader units doubles while the vertex processors remain unchanged. This brings Tegra 3's GPU core count up to 12. NVIDIA still hasn't embraced a unified architecture, but given how closely it's mimicking the evolution of its PC GPUs I wouldn't expect such a move until the next-gen architecture - possibly in Wayne.
Mobile SoC GPU Comparison | |||||||||||
Adreno 225 | PowerVR SGX 540 | PowerVR SGX 543 | PowerVR SGX 543MP2 | Mali-400 MP4 | GeForce ULP | Kal-El GeForce | |||||
SIMD Name | - | USSE | USSE2 | USSE2 | Core | Core | Core | ||||
# of SIMDs | 8 | 4 | 4 | 8 | 4 + 1 | 8 | 12 | ||||
MADs per SIMD | 4 | 2 | 4 | 4 | 4 / 2 | 1 | 1 | ||||
Total MADs | 32 | 8 | 16 | 32 | 18 | 8 | 12 | ||||
GFLOPS @ 200MHz | 12.8 GFLOPS | 3.2 GFLOPS | 6.4 GFLOPS | 12.8 GFLOPS | 7.2 GFLOPS | 3.2 GFLOPS | 4.8 GFLOPS | ||||
GFLOPS @ 300MHz | 19.2 GFLOPS | 4.8 GFLOPS | 9.6 GFLOPS | 19.2 GFLOPS | 10.8 GFLOPS | 4.8 GFLOPS | 7.2 GFLOPS |
Per core performance has improved a bit. NVIDIA worked on timing of critical paths through the GPU's execution units to help it run at higher clock speeds. NVIDIA wouldn't confirm the target clock for Tegra 3's GPU other than to say it was higher than Tegra 2's 300MHz. Peak floating point throughput per core is unchanged (one MAD per clock), but each core should be more efficient thanks to larger caches in the design.
A combination of these improvements as well as newer drivers are what give Tegra 3's GPU its 2x - 3x performance advantage over Tegra 2 despite only a 50% increase in overall execution resources. In pixel shader bound scenarios, there's an effective doubling of execution horsepower so the 2x gains are more believable there. I don't expect many games will be vertex processing bound so the lack of significant improvement there shouldn't be a big issue for Tegra 3.
Ready for Gaming: Stereoscopic 3D and Expanded Controller Support
Tegra 3 now supports stereoscopic 3D for displaying content from YouTube, NVIDIA's own 3D Vision Live website and some Tegra Zone games. In its port of Android, NVIDIA has also added expanded controller support for PS3, Xbox 360 and Wii controllers among others.
Tegra 3 Video Encoding/Decoding and ISP
There's unfortunately not too much to go on here, especially not until we have some testable hardware in hand, but NVIDIA is claiming a much improved video decoder and more efficient video encoder in Tegra 3.
Tegra 3's video decoder can accelerate 1080p H.264 high profile content at up to 40Mbps, although device vendors can impose their own bitrate caps and file limitations on the silicon. NVIDIA wouldn't go into greater detail as to what's changed since Tegra 2, other than to say that the video decoder is more efficient. The video encoder is capable of 1080p H.264 base profile encode at 30 fps.
The Image Signal Processor (ISP) in Tegra 3 is twice as fast as what was in Tegra 2 and NVIDIA promised more details would be forthcoming (likely alongside the first Tegra 3 smartphone announcements).
Memory Interface: Still Single Channel, DDR3L-1500 Supported
Tegra 3 supports higher frequency memories than Tegra 2 did, but the memory controller itself is mostly unchanged from the previous design. While Tegra 2 supported LPDDR2 at data rates of up to 600MHz, Tegra 3 increases that to LPDDR2-1066 and DDR3-L is supported at data rates of up to 1500MHz. The memory interface is still only 32-bits wide, resulting in far less theoretical bandwidth than Apple's A5, Samsung's Exynos 4210, TI's OMAP 4, or Qualcomm's upcoming MSM8960. This is particularly concerning given the increase in core count as well as GPU execution resources. NVIDIA doesn't expect memory bandwidth to be a limitation, but I can't see how that wouldn't be the case in 3D games. Perhaps it's a good thing that Infinity Blade doesn't yet exist for Android.
SATA II Controller: On Die
Given Tegra 3 will find itself in convertible Windows 8 tablets, this next feature makes a lot of sense. NVIDIA's latest SoC includes an on-die SATA II controller, a feature that wasn't present on Tegra 2.
94 Comments
View All Comments
Lucian Armasu - Wednesday, November 9, 2011 - link
Those probably use more power, too, so they wouldn't be suited for tablets and smartphones anyway. Tegra 3 is the first quad core to be optimized for them.jeremyshaw - Wednesday, December 21, 2011 - link
about as relevent as claiming the iPad 2 GPU doesn't matter since it doesn't use Android.jeremyshaw - Friday, December 16, 2011 - link
PS Vita is going on sale this Sat in Japan. For the rest of the world.... sucks to be you :pDraiko - Wednesday, November 9, 2011 - link
With a 3-5 hour battery life per charge. Disgusting.Shadowmaster625 - Wednesday, November 9, 2011 - link
Probably only 1 hour playing a game using the unreal engine or similar.tipoo - Wednesday, November 16, 2011 - link
They said 3-5 hours of gameplay on the Vita, other stuff is more.tipoo - Saturday, March 10, 2012 - link
Which is also what you get while gaming on any smartphone, if not less by the way.GeekBrains - Wednesday, November 9, 2011 - link
Let's wait and see how it affects the real world bandwidth requirements..dagamer34 - Wednesday, November 9, 2011 - link
Seems there's also a "lot of concern" too over the unchanged aspects of the Tegra 3 chip. They're shoving this entire design onto a 40nm process where every other competitor is focusing on 28nm which means greater power consumption at some point. Also, when you compare the numbers on the GPU, it seems that nVidia's got a rather weak offering comparing to the competition, which is kind of sad for a GPU company. What gives?B3an - Wednesday, November 9, 2011 - link
It's because of 40nm, with any more GPU power the chip would be even bigger. It's looking like there will be a 28nm version of Tegra 3 next year, but in order to be the first out with a quadcore SoC they have decided to use 40nm for now.