Re-evaluating Strategy, Creating the RV770 in 2005

Remembering what lead to success rather than the success itself is generally more important, and around 2005 ATI had another R300 moment. What made R300 successful was ATI re-evaluating the way it made GPUs and deciding on something that made sense. At the time, it made sense for ATI to work towards building the biggest chip possible, win at the high end and translate that into better, more competitive products at all other price points. It is worth mentioning that part of R300’s continued success was due to the fact that NVIDIA slipped up royally with the GeForce FX, it was the perfect storm and ATI capitalized. ATI built the biggest chip and NVIDIA had no real answer for some time to come.

Just as Intel bumped into the power wall when it tried to ramp Pentium 4 clock speeds to ridiculous levels, ATI was noticing that GPUs were getting a little too big for comfort. Design cycles were getting longer, die size was growing and financially there were some things that didn’t quite make sense when it came to making these large GPUs.

ATI asserted that a very large GPU, without the use of repair structures or harvesting (two techniques I’ll describe in a bit) may only have a 30% yield. That means for every 100 GPUs produced on a single wafer, only 30% of them would be fully functional and could be sold as advertised. Manufacturing these complex circuits is particularly expensive, those fab plants easily cost a couple of billion dollars to build and thus having most of your wafer go to waste isn’t really a good way of running a business.

Thankfully there are ways to improve that crappy 30% yield to a value north of 90%. The first is a technique generally known as repairability. The idea behind repairability is simple: build redundancy into your design. If you have a unit with 10 shader processors, actually build 11 but use one as a spare should there be a defect in any of the remaining processors. The same technique is often used for on-die memory, include additional cells so that a defect in one part of a cache won’t render the entire chip unusable. There are tradeoffs here however, if you build in too much repairability then you run the risk of having a die that’s large but offers no additional performance benefit. If you don’t build in enough repairability then your yield suffers.

Harvesting is another technique that all of you are quite familiar with, although its street name is feature binning. The idea here is that you assume that only a small percentage of the die on a wafer will be completely functional, but instead of throwing away the ones that aren’t fully functional, you disable features and sell them as a lower end part. For example, if your target architecture has 10 shader processors but only 30% of your production will have 10 working shader processors but 50% of the production will have 8 working units you’d sell a model with 10 SPs and a model with 8 SPs, the latter being at a reduced cost. This way instead of throwing away 70% of the wafer, you only throw away 20% - and if possible you could make a third SKU with fewer number of functional SPs and use close to 100% of the wafer.

Yields do improve over time, and what eventually happens if you build a product relying on harvesting is you hurt yourself financially. In the example above where you have two configurations of the same die, yields will eventually improve to the point where your 8 SP die could just as easily have 10 functional SPs but you have to sell them as reduced functionality parts because you’ve built up market demand for them. In a sense, you’re selling something worth $1 for $0.80. You could always create a new version of the chip with a smaller die, but that takes additional engineering resources, time and money.

The most recent public example of die harvesting was actually with NVIDIA’s GT200. The GeForce GTX 260 was simply a harvested version of the GTX 280 with 192 SPs vs. 240. As yields improved, NVIDIA introduced the GeForce GTX 260 Core 216 with 216 SPs. Note that NVIDIA didn’t use any repairability for the shader processors on GT200 there are no more than 240 functional SPs on a GT200 die, but that’s because NVIDIA would rely on harvesting anyway - if any of the 240 SPs didn’t work the chip would be branded as a GTX 260 or Core 216.

This is in stark contrast to RV770 where both versions of the GPU were functionally identical, the only differences were clock speeds and power requirements. But from a die standpoint, ATI didn’t have to sell any reduced versions of the chip to keep yields high.

Note that whether or not a company has to rely on harvesting doesn’t really impact the end user. In this case, the GeForce GTX 260 Core 216 actually benefitted the end user as it manages to deliver the same sort of value that AMD does with the Radeon HD 4870. It isn’t ideal for NVIDIA financially and if a company has to rely on harvesting for too long it will eventually take its toll, but I suspect that in the GT200 case NVIDIA will bail itself out with a 55nm revision of GT200 before things get too bad.

ATI didn’t want to build a GPU that would rely on excessive repair and harvesting to keep yields high. And then came the killer argument: building such a GPU was no longer in the best interests of its customers.

Sidenote: Building a GPU

Before we get too far down the rabbit hole it’s worth adding some perspective. ATI’s RV770 design took three years of work, that means ATI started in 2005. It takes about a year for manufacturability from tapeout to final product ship, another 1 - 1.5 years for design and another year for architecture.

The team that I met with in Santa Clara was talking about designs that would be out in 2012, we’re talking 4 TFLOPS of performance here, 4x the speed of RV770.

Decisions being made today are going to impact those products and in a sense it’s a big guessing game, ATI has no idea what NVIDIA will have in 2012 and NVIDIA has no idea what ATI will have. Each company simply tries to do the best it can for the customers and hopes they’ve got the right mix of performance, price and power.

To give you an idea of the intensity of some of these debates, Carrell debated, every evening, for three hours, for three weeks, the amount of repairability that would go into the RV770. Building redundant structures in the RV770 was an even bigger deal than before because ATI was going to be working within serious die constraints, simply making the chip bigger wasn’t an option. Repair structures in the RV770 wouldn’t add any performance but would increase the die size, on an already large chip that’s fine, but on a chip that’s supposed to target the sweet spot and can’t grow without limit it’s a big deal.

The Beginning: The Shot Heard Around the World Building a GPU for the Masses
POST A COMMENT

115 Comments

View All Comments

  • yourwhiteshadow - Thursday, December 04, 2008 - link

    absolutely brilliant. i've always read anandtech instead of tomshardware because of objective reviews. i was reading an intel review, and people were questioning the objectivity of anandtech. while some might could look at this as praising ATI/AMD, i would definitely say this was a very objective view of what happened. seriously, one of the BEST articles i've read since the 4850/4870 review. Reply
  • kevyeoh - Thursday, December 04, 2008 - link

    I've been reading anandtech for years and there wasn't any article that makes me wanna read every single word of it. Usually i will read the forewords and then skip on to the Conclusion. But for this article, i really read every single words! period! Anandtech rocks! Reply
  • nitemareglitch - Thursday, December 04, 2008 - link

    I was actually getting a little bored with the articles around here, until I read this one. Great job, I loved reading this story!! Reply
  • lchyi - Thursday, December 04, 2008 - link

    This is by far the best (and most insightful) article I have read here to date Anand. It sounds like you put in a ton of thought to it and I have never flown through 7,500 words as quick as that read. Congrats to the ATI guys for their successful gamble on the RV770. The last three years must have been an extremely interesting experience for them and their engineers. Reply
  • joshjnm - Thursday, December 04, 2008 - link

    Great article I will bandwagon with the rest of you and agree this is one of the best articles I've read in a while.

    Reply
  • josh6079 - Thursday, December 04, 2008 - link

    I thoroughly enjoyed the article. Last time I was really involved with graphics cards was when the X1900's were in full swing and G80 was on everyone's mind. The history told in the article helped bring me up to pace as to what has transpired since I stopped gaming as much. I can remember how the Video card section used to be here on the forums with the trolls and constant flames. Two camps of people cheered on for one or the other competitors instead of realizing that they should be cheering for competition itself.

    Great job ATI, Nvidia - what's next?
    Reply
  • Seikent - Thursday, December 04, 2008 - link

    Very good article, most of these interesting background stories are written in books, but a lot of years latter.

    Something, that is not mentioned, is that it seems that AMD didn't affect ATI in any way (technically speaking). Many thought that the R600 failure had something to do with AMD.
    Reply
  • BSMonitor - Thursday, December 04, 2008 - link

    Awesome article.

    I am definately a performance/mainstream kinda guy in this market. Definately love the competition. I started my first build with a Geforce 4200Ti, moved up to the infamous 9700Pro, followed by X1900, and now 4850HD...

    It is good to see that the ATI/AMD didn't damage ATI as a whole. Rock on guys! Love those cheap kick ass Crossfire cards! Go 4850HD x2.
    Reply
  • dmer - Thursday, December 04, 2008 - link

    as a long time reader of anand I never felt the need to register an account; however, after reading your article I felt compelled to create an account just to commend you on an excellent article.

    we need more articles that give us insight into business decisions like this. job well done mate!
    Reply
  • johnkwright - Thursday, December 04, 2008 - link

    Anand,

    I've been a long time reader of AnandTech but I especially liked this article. It was interesting to get a peek behind the curtain to see what challenges companies face when making these tough decisions. Hopefully more companies take a chance and share more of their stories with this site. Keep up the good work.

    Regards,
    John Wright
    Reply

Log in

Don't have an account? Sign up now