The Fiji GPU: Go Big or Go Home

Now that we’ve had a chance to take a look at the architecture backing Fiji, let’s talk about the Fiji GPU itself.

Fiji’s inclusion of High Bandwidth Memory (HBM) technology complicates the picture somewhat when talking about GPUs. Whereas past GPUs were defined by the GPU die itself and then the organic substrate package it sits on, the inclusion of HBM requires a third layer, the silicon interposer. The job of the interposer is to sit between the package and the GPU, serving as the layer that connects the on-package HBM memory stacks with the GPU. Essentially a very large chip without any expensive logic on it, the silicon interposer allows for finer, denser signal routing than organic packaging is capable of, making the ultra-wide 4096-bit HBM bus viable for the first time.

We’ll get to HBM in detail in a bit, but it’s important to call out the impact of HBM and the interposer early, since they have a distinct impact on how Fiji was designed and what its capabilities are.

As for Fiji itself, Fiji is unlike any GPU built before by AMD, and not only due to the use of HBM. More than anything else, it’s simply huge, 596mm2 to be precise. As we mentioned in our introduction, AMD has traditionally shied away from big chips, even after the “small die” era ended, and for good reason. Big chips are expensive to develop, expensive to produce, take longer to develop, and yield worse than small chips (this being especially the case early-on for 40nm). Altogether they’re riskier than smaller chips, and while there are times where they are necessary, AMD has never reached this point until now.

The end result is that for the first time since the unified shader era began, AMD has gone toe-to-toe with NVIDIA on die size. Fiji’s 596mm2 die size is just 5mm2 (<1%) smaller than NVIDIA’s GM200, and more notably still hits TSMC’s 28nm reticle limit. TSMC can’t build chips any bigger than this; Fiji is as big a chip as AMD can order.

AMD Big GPUs
  Die Size Native FP64 Rate
Fiji (GCN 1.2) 596mm2 1/16
Hawaii (GCN 1.1) 438mm2 1/2
Tahiti (GCN 1.0) 352mm2 1/4
Cayman (VLIW4) 389mm2 1/4
Cypress (VLIW5) 334mm2 1/5
RV790 (VLIW5) 282mm2 N/A

Looking at Fiji relative to AMD’s other big GPUs, it becomes very clear very quickly just how significant this change is for AMD. When Hawaii was released in 2013 at 438mm2, it was already AMD’s biggest GPU ever for its time. And yet Fiji dwarfs it, coming in at 158mm2 (36%) larger. The fact that Fiji comes at the latter-half of the 28nm process’s life time means that such a large GPU is not nearly as risky now as it would have been in 2011/2012 (NVIDIA surely took some licks internally on GK110), but still, nothing else we can show you today can really sell the significance of Fiji to AMD as much as the die size can.

And the fun doesn’t stop there. Along with producing the biggest die they could, AMD has also more or less gone the direction of NVIDIA and Maxwell in the case of Fiji, building what is unambiguously the most gaming/FP32-centric GPU the company could build. With GCN supporting power-of-two FP64 rates between 1/2 and 1/16, AMD has gone for the bare minimum in FP64 performance that their architecture allows, leading to a 1/16 FP64 rate on Fiji. This is a significant departure from Hawaii, which implemented native support for ½ rate, and on consumer parts offered a handicapped 1/8 rate. Fiji will not be a FP64 powerhouse – its 4GB of VRAM is already perhaps too large of a handicap for the HPC market – so instead we get AMD’s best FP32 GPU going against NVIDIA’s best FP32 GPU.

AMD’s final ace up their sleeve on die size is HBM. Along with HBM’s bandwidth and power benefits, HBM is also much simpler to implement, requiring less GPU space for PHYs than GDDR5 does. This is in part due to the fact that HBM stacks have their own logic layer, distributing some of the logic on to each stack, and furthermore a benefit of the fact that the signaling logic that remains doesn’t have to be nearly as complex since the frequencies are so much lower. 4096-bits of HBM PHYs still takes up a fair bit of space – though AMD won’t tell us how much – but it’s notably lower than the amount of space AMD was losing to Hawaii’s GDDR5 memory controllers.

The end result is that not only has AMD built their biggest GPU ever, but they have done virtually everything they can to maximize the amount of die space they get to allocate to FP32 and rendering resources. Simply put, AMD has never reached so high and aimed for parity with NVIDIA in this manner.

Ultimately this puts Fiji’s transistor count at 8.9 billion transistors, even more than the 8 billion transistors found in NVIDIA’s GM200, and, as expected, significantly more than Hawaii’s 6.2 billion. Interestingly enough, on a relative basis this is almost exactly the same increase we saw with Hawaii; Fiji packs in 43.5% more transistors than Hawaii, and Hawaii packed in 43.9% more transistors than Tahiti. So going by transistors alone, Fiji is very much to Hawaii what Hawaii was to Tahiti.

Finally, as large as the Fiji GPU is, the silicon interposer it sits on is even larger. The interposer measures 1011mm2, nearly twice the size of Fiji. Since Fiji and its HBM stacks need to fit on top of it, the interposer must be very large to do its job, and in the process it pushes its own limits. The actual interposer die is believed to exceed the reticle limit of the 65nm process AMD is using to have it built, and as a result the interposer is carefully constructed so that only the areas that need connectivity receive metal layers. This allows AMD to put down such a large interposer without actually needing a fab capable of reaching such a large reticle limit.

What’s interesting from a design perspective is that the interposer and everything on it is essentially the heart and soul of the GPU. There is plenty of power regulation circuitry on the organic package and even more on the board itself, but within the 1011mm2 floorplan of the interposer, all of Fiji’s logic and memory is located. By mobile standards it’s very nearly an SoC in and of itself; it needs little more than external power and I/O to operate.

Fiji’s Architecture: The Grandest of GCN 1.2 Fiji’s Layout
Comments Locked

458 Comments

View All Comments

  • Samus - Saturday, July 4, 2015 - link

    Being an NVidia use for 3 generations, I'm finding it hard to ignore this cards value, especially since I've invested $100 each on my last two NVidia cards (including my SLI setup) adding liquid cooling. The brackets alone are $30.

    Even if this card is less efficient per watt than NVidia's, the difference is negligible when considering kw/$. It's like comparing different brand of LED bulbs, some use 10-20% less energy but the overall value isn't as good because the more efficient ones cost more, don't dim, have a light buzz noise, etc.

    After reading this review I find the Fury X more impressive than I otherwise would have.
  • Alexvrb - Sunday, July 5, 2015 - link

    Yeah a lot of reviews painted doom and gloom but the watercooler has to be factored into that price. Noise and system heat removal of the closed loop cooler are really nice. I still think they should launch the vanilla Fury at $499 - if it gets close to the performance of the Fury X they'll have a decent card on their hands. To me though the one I'll be keeping an eye out for is Nano. If they can get something like 80% of the performance at roughly half the power, that would make a lot of sense for more moderately spec'd systems. Regardless of what flavor, I'll be interested to see if third parties will soon launch tools to bump the voltage up and tinker with HBM clocks.
  • chizow - Monday, July 6, 2015 - link

    Water cooling if anything has proven to be a negative so far for Fury X with all the concerns of pump whine and in the end where is the actual benefit of water cooling when it still ends up slower than 980Ti with virtually no overclocking headroom?

    Based on Ryan's review Fury Air we'll most likely see the downsides of leakage on TDP and its also expected to be 7/8th SP/TMU. Fury Nano also appears to be poised as a niche part that will cost as much if not more than Fury X, which is amazing because at 80-85% of Fury X it won't be any faster than the GTX 980 at 1440p and below and right in that same TDP range too. It will have the benefit of form factor but will that be enough to justify a massive premium?
  • Alexvrb - Monday, July 6, 2015 - link

    You can get a bad batch of pumps in any CLC. Cooler Master screwed up (and not for the first time!) but the fixed units seem to be fine and for the units out there with a whine just RMA them. I'm certainly not going to buy one, but I know people that love water cooled components and like the simplicity and warranty of a CL system.

    Nobody knows the price of the Nano, nor final performance. I think they'd be crazy to price it over $550 even factoring in the form factor - unless someone releases a low-profile model, then they can charge whatever they want for it. We also don't know final performance of Fury compared to Fury X, though I already said they should price it more aggressively. I don't think leakage will be that big of an issue as they'll probably cap thermals. Clocks will vary depending on load but they do on Maxwell too - it's the new norm for stock aircooled graphics cards.

    As for overclocking, yeah that was really terrible. Until people are able to tinker with voltage controls and the memory, there's little point. Even then, set some good fan profiles.
  • Refuge - Thursday, July 23, 2015 - link

    To be honest, the wine I've seen on these isn't anything more than any other CLC I've ever seen in the wild.

    I feel like this was blown a bit out of proportion. Maybe I'm going deaf, maybe I didn't see a real example. I'm not sure.
  • tritiumosu3 - Thursday, July 2, 2015 - link

    "AMD Is nothing if not the perineal underdog"
    ...
    perineal =/= perennial! You should probably fix that...
  • Ryan Smith - Thursday, July 2, 2015 - link

    Thanks. Fixed. It was right, and then the spell-checker undid things on me...
  • ddriver - Thursday, July 2, 2015 - link

    I'd say after the Hecktor RuiNz fiasco, "perpetual underdog" might be more appropriate.
  • testbug00 - Sunday, July 5, 2015 - link

    Er, what fiasco did Hector Ruiz create for AMD?
  • Samus - Monday, July 6, 2015 - link

    I'm wondering the same thing. When Hector Ruiz left Motorola, they fell apart, and when he joined AMD, they out-engineered and out-manufactured Intel with quality control parity. I guess the fiasco would be when Hector Ruiz left AMD, because then they fell apart.

Log in

Don't have an account? Sign up now