AMD Beema/Mullins Architecture & Performance Previewby Anand Lal Shimpi on April 29, 2014 12:00 AM EST
When AMD launched its Kabini and Temash APUs last year it delivered a compelling cost/performance story, but its power story wasn’t all that impressive. Despite being built out of relatively low power components, nearly all of AMD’s entry level APUs carried 15W TDPs, with a couple weighing in at 8 - 9W and only a single 1GHz dual-core part dropping down to 3.9W. By comparison, Intel was shipping full blown Haswell Ultrabook parts at 15W - offering substantially better CPU performance, in a similar thermal envelope (although at a higher cost). The real disruption for AMD was Intel’s Bay Trail, which showed up with a similar looking micro architecture running at substantially higher clock speeds and TDPs below 8W.
AMD seemed to have all of the right pieces to build a power efficient mobile SoC, but for some reason we weren’t seeing it. Today that begins to change with the the successors to Kabini and Temash.
Codenamed Beema and Mullins, these are the 2014 updates to Kabini and Temash (respectively). Beema is aimed at entry level notebooks, while Mullins targets tablets. For now, both are designed for Windows machines. Although I suspect we’ll eventually see AMD address the native Android market head on, for now AMD is relying on running Android on top of Windows for those who really want it. No word on if/when we’ll get a socketed Beema for entry level desktops.
Like their predecessors, Beema and Mullins combine four low power AMD x86 cores (Puma+ this time, instead of Jaguar) with 128 GCN based Radeon GPU cores. AMD will continue to offer a couple of dual-core SKUs, but they are harvested from a quad-core die. AMD remains unwilling to release official die area figures, but there is a slight increase in transistor count:
|AMD/Intel Transistor Count & Die Area Comparison|
|SoC||Process Node||Transistor Count||Die Area|
|AMD Zacate||TSMC 40nm||450M+||75mm2|
|AMD Kabini/Temash||TSMC 28nm||914M||~107mm2 (est)|
|AMD Beema/Mullins||GF 28nm||930M||~107mm2 (est)|
|AMD Llano||GF 32nm SOI||1.18B||228mm2|
|AMD Trinity/Richland||GF 32nm SOI||1.30B||246mm2|
|AMD Kaveri||GF 28nm SHP||2.41B||245mm2|
|Intel Haswell (4C/GT2)||Intel 22nm||1.40B||177mm2|
I’d expect a similar die size to Kabini/Temash. It’s interesting to note that these SoCs have a transistor count somewhere south of Apple’s A7.
Puma+ is based on the same micro architecture as Jaguar. We’re still looking at a 2-wide OoO design with the same number of execution units and data structures inside the chip. The memory interface remains unchanged as well at 64-bits wide. These new SoCs are still built on the same 28nm process as their predecessor. The process however has seen some improvements. Not only are both the CPU and GPU designs slightly better optimized for lower power operation, but both benefit from improvements to the manufacturing process resulting in substantial decreases in leakage current.
AMD claims a 19% reduction in core leakage/static current for Puma+ compared to Jaguar at 1.2V, and a 38% reduction for the GPU. The drop in leakage directly contributes to a substantially lower power profile for Beema and Mullins.
AMD also went in and tweaked the SoC’s memory interface. Kabini/Temash had a standard PC-like DDR3 memory interface. All of the complexity required for broad memory module compatibility and variations in trace routing was handed by the controller itself. This not only added complexity to the DDR3 interface but power as well. With Beema and Mullins, AMD took a page from the smartphone SoC design guide and traded flexibility for power. These platforms now ship with more strict guidelines as to what sort of memory can be used on board and how traces must be routed. The result is a memory interface that shaves off more than 500mW when in this more strict, low power mode. OEMs looking to ship a design with socketed DRAM can still run the memory interface in a higher power mode to ensure memory compatibility.
These SoCs won’t be available in a PoP configuration unfortunately - OEMs will have to rely on discrete DRAM packages rather than a fully integrated solution. Beema/Mullins also show up to a 200mW reduction in power consumed by the display interface compared to Kabini/Temash.
The combination of all of this is 20% lower idle power compared to the previous generation of AMD entry level and low power APUs. AMD put together a nice graph illustrating its progress over the years:
Beema and Mullins are definitely in a good place, however they still do consume more power at idle than the smartphone SoCs we typically find in iOS and Android tablets. AMD isolated APU power for the graph above and is using an “eReader” workload (aka display on but not animating, system otherwise idle). It just so happens I gathered similar data for our 2013 Nexus 7 review. The workloads and measurements are different (AMD isolates APU power, I’m looking at total platform power minus display) but it’s enough to put things in perspective:
AMD has dropped power consumption considerably over the years, but it’s still not as power efficient as high end mobile silicon.
AMD sees no value in supporting Microsoft's Connected Standby standard at this point, which makes sense given the limited success of Windows 8 tablets. Once again this seems to point to AMD eventually adopting Android for its tablet aspirations.
Looking forward, AMD has more tricks up its sleeve to continue to drive power down. Most interesting on the list? We’ll see an integrated voltage regulator (ala Haswell’s FIVR) from AMD in 2015.
Post Your CommentPlease log in or sign up to comment.
View All Comments
saneblane - Tuesday, April 29, 2014 - linkUnlock That 2.4GHZ Beema Pls. It sure would be nice to get an Amd quadcore 3GHZ at 25 watts.
Amd Should increase the highend on these and kill of Low Power Kaveri.
MrHorizontal - Tuesday, April 29, 2014 - linkInteresting little package that.
But very little detail on the memory controller - how wide is it? From what I can see it's just single channel. Personally I think these Puma cores would serve AMD a lot better as a low power Opteron CPU than ARM would, equivalent to Intel's Avoton package, provided they can use a significant amount of memory on a system - a single channel won't cut it.
MrSpadge - Tuesday, April 29, 2014 - linkSingle channel, since it's I/O compatible with the previous chips.
mfoley93 - Wednesday, April 30, 2014 - linkThe author should add this, to the article, not everyone that is interested keeps up on this stuff closely enough to remember all of the details from 8 months ago.
piroroadkill - Tuesday, April 29, 2014 - linkMakes you once again realise how wimpy the CPU is in the Xbox One and PS4.
8 Jaguar cores. More crap is still crap.
These cores are far better than that, and still wouldn't be considered high end.
H2323 - Tuesday, April 29, 2014 - link8 Jag cores that have access to fast memory are plenty good for a multi-threaded game
tipoo - Tuesday, April 29, 2014 - linkDisagreed. It was a matter of performance for cost, and even though each Jaguar core may perform half as well as a high end desktop core, they were able to fit 8 cores into less die space than those bigger cores would have taken. If a developer takes good advantage of multithreading they'll be fine for a while.
Antronman - Wednesday, April 30, 2014 - linkBut they won't considering most engines used are multiplatform engines and the majority of the games made with those engines are single threaded.
The performance sucks, no matter how you look at it.
Graphics have a big effect on performance, and the graphical power on the new consoles is...less than enough.
lmcd - Friday, May 2, 2014 - linkAre you kidding? Engines mean that things can be more threaded as it's more abstracted and so more time can be spent on threading (as opposed to rewrites and higher-level coding that a smaller team would deal with).
coburn_c - Tuesday, April 29, 2014 - linkOh look another AMD product launch with regressive performance... and yet another AMD product launch where their power usage is double that of the competition. Still I suppose it's an improvement, they could be at 4x the power usage now if they hadn't finally done some work. Well I suppose they can just lay off another 25% of the company, that'll sure help close the gap..