Slashdot Mirror


NVIDIA GTX 970 Specifications Corrected, Memory Pools Explained

Vigile writes Over the weekend NVIDIA sent out its first official response to the claims of hampered performance on the GTX 970 and a potential lack of access to 1/8th of the on-board memory. Today NVIDIA has clarified the situation again, this time with some important changes to the specifications of the GPU. First, the ROP count and L2 cache capacity of the GTX 970 were incorrectly reported at launch (last September). The GTX 970 has 52 ROPs and 1792 KB of L2 cache compared to the GTX 980 that has 64 ROPs and 2048 KB of L2 cache; previously both GPUs claimed to have identical specs. Because of this change, one of the 32-bit memory channels is accessed differently, forcing NVIDIA to create 3.5GB and 0.5GB pools of memory to improve overall performance for the majority of use cases. The smaller, 500MB pool operates at 1/7th the speed of the 3.5GB pool and thus will lower total graphics system performance by 4-6% when added into the memory system. That occurs when games request MORE than 3.5GB of memory allocation though, which happens only in extreme cases and combinations of resolution and anti-aliasing. Still, the jury is out on whether NVIDIA has answered enough questions to temper the fire from consumers.

113 comments

  1. Don't worry, AMD would never lie to us... by Anonymous Coward · · Score: 0, Insightful

    Right, right?

    Ah you can't tell, but I'm not able to hold a straight face.

    1. Re:Don't worry, AMD would never lie to us... by Dins · · Score: 1

      AMD isn't involved here. This is NVIDIA...

    2. Re:Don't worry, AMD would never lie to us... by meerling · · Score: 1

      I don't hold Nvidia in high regard, but it's still higher than ATI, and besides, how many other graphics vendors do gamers have to go to?
      (And before you say it, Intel is only the choice of idiots when it comes to graphics for gamers. Maybe someday they'll get their header out of their asterisk, but it hasn't happened yet.)

    3. Re: Don't worry, AMD would never lie to us... by Anonymous Coward · · Score: 0

      Whoosh.

    4. Re: Don't worry, AMD would never lie to us... by nicholas22 · · Score: 1

      Wow straight to the "race to the bottom" hey mate? Your masters have trained you well... Why instead of condemning false advertising, do you excuse it as a common practice..?

    5. Re: Don't worry, AMD would never lie to us... by Anonymous Coward · · Score: 0

      Except I'm recognizing it as a widespread practice, not excusing it.

      The lack of a straight face is more of a mocking one, if you could only see it.

    6. Re: Don't worry, AMD would never lie to us... by Anonymous Coward · · Score: 0

      There is a 200 dollar price difference for the cards on new egg.... You don't stay in business by undercutting yourself.. Anyone who thought the cards would be identical is beyond retarded.

    7. Re:Don't worry, AMD would never lie to us... by Anonymous Coward · · Score: 0

      Well, ATI is long since dead, sadly. AMD killed them.

      for what it's worth, I worked with a team that decided which parts of ATI chips should be "harvested" (nVidia calls it "floor-sweeping"); that is, which sub-units could be disabled for different SKUs to satisfy cost/yield/perf requirements. The design teams worked to make the sub-unit harvested work, yes, and may have been peripherally involved in identifying most-likely or most-performant options. But while it was far from secret, most designers only knew the config/specs of the "full" version of the chip. They didn't care that one of this or three of that were harvested out for yield. They just knew the full version had X of this and Y of that.

      It's like repairable SRAMs on the chip. there may be 2.75MB of SRAM bitcells on the die, but only 2.5MB that is "usable". Don't expect the average designer to know how many redundant bitcells were dropped down. Nor will they know how many tapcells are in their design, nor how many routing tracks, or possibly how many flops (for datapath units that have tool-driven retiming).

      This whole thing is sad. It almost sounds like a fanboi fire that may have been professionally stoked. I hope the folks I know that are still at AMD didn't do that, or have anything to do with this, because the pot shouldn't really be talking about the kettle, you know?

    8. Re: Don't worry, AMD would never lie to us... by Anonymous Coward · · Score: 0

      But still. Even if AMD has lied in the past, that does not make NVIDIA lying acceptable. It's like when people defend bad quality of open source with "too bad Windows isn't any better". Saying that won't still do a shit to improve OSS.

    9. Re: Don't worry, AMD would never lie to us... by gl4ss · · Score: 1

      There is a 200 dollar price difference for the cards on new egg.... You don't stay in business by undercutting yourself.. Anyone who thought the cards would be identical is beyond retarded.

      ever heard of Fire and Quadro series... ?

      --
      world was created 5 seconds before this post as it is.
    10. Re: Don't worry, AMD would never lie to us... by Anonymous Coward · · Score: 0

      He's not defending it, nor calling it acceptable. He's just stopping the inevitable AMD fanboys from jumping all over it.

    11. Re: Don't worry, AMD would never lie to us... by Anonymous Coward · · Score: 0

      You say all this like its some shady underhanded practice, then you said it yourself, it's about yields.

      You find the same practice in almost any product, even where a single model is offered, something had to be cut from the design to make manufacturing costs and yields more reasonable.

      Only difference here is several design revisions are offered at once, and geeks get butthurt over technicalities.

      If they put all their design efforts into the low end cards they'd be racing to the bottom. They cost less and perform less, and if performance/$ is OK, what else should a normal person care about.

  2. They are partnering with SOE on a fix by mandark1967 · · Score: 2, Insightful

    You pay for an airdrop containing the extra ROPS and Cache. It's contested, though, so you may or may not get it.

    --
    Sig Follows: "Suppose you were an idiot. And suppose you were a member of Congress. But I repeat myself." -- Mark Twain
  3. Option? by ArcadeMan · · Score: 1

    The smaller, 500MB pool operates at 1/7th the speed of the 3.5GB pool and thus will lower total graphics system performance by 4-6% when added into the memory system. That occurs when games request MORE than 3.5GB of memory allocation though, which happens only in extreme cases and combinations of resolution and anti-aliasing.

    How about giving us the option to either always be able to run at maximum speed (disable that last 0.5GiB) or always let the software use the full 4GiB (at the cost of speed if more than 3.5GiB is required).

    1. Re:Option? by jandrese · · Score: 1

      Won't the option be to either let the GPU use the extra 1/7 speed memory, or force the data back out to system memory over the PCIe bus at a much lower speed? Outside of benchmarks, I don't think many applications are going to be demanding that extra memory anyway.

      --

      I read the internet for the articles.
    2. Re:Option? by Anonymous Coward · · Score: 2, Informative

      There's really no point to doing that. If you disable the memory and run at high resolutions with ultra textures and AA that would cause you to break that 3.5 GB barrier, your performance would just tank because you are exchanging with main memory. In other words, the performance of the card is exactly at least what you would get from a 3.5 GB card. That extra 500 MB isn't hurting anything.

    3. Re:Option? by gman003 · · Score: 1

      There might be cases where an application queries how much memory is available, then allocates all of it to use as caching. If the driver doesn't manage that memory well (putting least-used data in the slower segment), that could cause performance to be lower than if it were forced to 3.5GB only.

      That said, nobody seems to have found any applications where the memory management malfunctions like that, so it's more a theoretical quibble than actual at this point. And, knowing Nvidia, they'd just patch the driver so it would report a lower memory amount to that app only (they unfortunately tend to fill their drivers with exceptions or rewritten shaders to make big-name games run faster).

    4. Re:Option? by exomondo · · Score: 1

      How about giving us the option to either always be able to run at maximum speed (disable that last 0.5GiB) or always let the software use the full 4GiB (at the cost of speed if more than 3.5GiB is required).

      Because if it doesn't use more than 3.5GB then the performance is no different and if it does use more than 3.5GB then it will use that slower 0.5GB of additional video memory rather than using the even slower system memory. Disabling that extra 0.5GB will do nothing for performance except make it worse in cases where more than 3.5GB is used.

    5. Re:Option? by Anonymous Coward · · Score: 0

      The problem is that you never know if the active set is over 3.5GB or not.

    6. Re:Option? by exomondo · · Score: 1

      And how does that impact either of those scenarios?

    7. Re:Option? by exomondo · · Score: 1

      There might be cases where an application queries how much memory is available, then allocates all of it to use as caching.

      As you say, that is really just theoretical. Doing that would be a very poor memory management system. Assuming that just because there is free memory you can allocate all of it to use for caching would be a silly thing to do. Even in the case where you can assume that your process has exclusive control and ownership of the memory pool no middleware is even going to do that as code outside that middleware but within that process could allocate GPU memory for some other use. So I doubt this would happen except in very contrived scenarios.

    8. Re:Option? by gigaherz · · Score: 1

      Consider it a 3.5GB graphics card, with 500mb of "last resort" memory.

    9. Re:Option? by Anonymous Coward · · Score: 0

      In a graphics scenario I agree with you , but in a coprocessor usage case looking at available memory and chunking work units into appropriate sizes is completely realistic....but there are better solutions than a 970 if that is your goal.

    10. Re:Option? by Anonymous Coward · · Score: 0

      Most OSes will allocate the vast majority of RAM to a disk cache, because unused RAM is wasted RAM.

      Android keeps tasks in RAM and kills off processes to free RAM up only when needed.
      Windows allocates a large disk cache, reducing the size when needed.

    11. Re:Option? by exomondo · · Score: 1

      Most OSes will allocate the vast majority of RAM to a disk cache, because unused RAM is wasted RAM.

      Yes, but that is completely different. That is the operating system and it is dealing with system RAM - which the operating system controls access to anyway. What we are talking about here is video memory and processes that do not exclusively control that video memory.

    12. Re:Option? by exomondo · · Score: 1

      Yes if you have a job manager in a dedicated compute environment that is reasonable, but as you say you aren't using a 970 in that case.

  4. has not answered the important question by ihtoit · · Score: 1

    What about those users (more than one, anecdotes are data not anomalies!) whose use causes the GPUs to attempt to address more than 3.5GB VRAM causing them to crash out? If what NVidia are claiming here according to TFS is accurate, then this should not be happening. It is happening, the 3.5GB roof is being hit hard and people are feeling it. What say you, NVidia?

    --
    Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    1. Re:has not answered the important question by JustNiz · · Score: 2, Informative

      >> causing them to crash out

      This is a blatantly misieading thing to say. The cards don't crash at all. The only thing that happens as a result of this is a properly handled decrease in real world performance compared to the 980.

      Are you seriously trying to claim that the 970 _should_ have the same performance as the 980?

    2. Re:has not answered the important question by ihtoit · · Score: 0

      no, I did not say that. The claim is that these cards, in the first instance, are being sold as 4GB cards. That's as may be, but the top 500MB is deliberately crippled (to turn a 980 into a 970? I don't get the logic) to the point where it can and does cause repeated and repeatable crashes when the 3.5GB ceiling is met under certain conditions, which is ENTIRELY doable when you have a multiple screen setup. That is the issue.

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    3. Re:has not answered the important question by ihtoit · · Score: 0

      The fix here would be to issue a firmware update that disables that slow 500MB*, and update the labelling on the card to reflect the fact that it's a 3.5GB card not a 4GB.

      *Ever run RAM of two different speeds in a desktop? Wonder where those crashes are coming from? It's not a case of the faster RAM waiting for the slower RAM, the slower stuff is tripping over trying to keep up with the faster stuff. It doesn't work in the same way as a PATA channel where the bus runs at the speed of the slowest device.

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    4. Re:has not answered the important question by JustNiz · · Score: 2

      >> where it can and does cause repeated and repeatable crashes

      I call bullshit. Please post credible references to people actually experiencing crashes while gaming as a result of this.

    5. Re:has not answered the important question by Anonymous Coward · · Score: 0

      The fix here would be to issue a firmware update that disables that slow 500MB*, and update the labelling on the card to reflect the fact that it's a 3.5GB card not a 4GB.

      *Ever run RAM of two different speeds in a desktop? Wonder where those crashes are coming from? It's not a case of the faster RAM waiting for the slower RAM, the slower stuff is tripping over trying to keep up with the faster stuff. It doesn't work in the same way as a PATA channel where the bus runs at the speed of the slowest device.

      Yes it does.

    6. Re:has not answered the important question by JustNiz · · Score: 1

      >> *Ever run RAM of two different speeds in a desktop? Wonder where those crashes are coming from?

      No I'm not that stupid. And yours is a *terrible* analogy. You're not meant to mix different speed ram for your system. At least it says so in every motherboard manual I've ever read, which is a LOT in over 30 years of building my own PCs. If you do then you are not only operating outside the design parameters of the motherboard maker, but cluless about computers.
      Also, GPU memory is functionally totally different than system memory. Fuirthermore unlike some idiot who mixes ram even though the manual says not to, this is a decision taken by the manufacturer and until you post credible links proving otherwise, I'm going to stick with the fact that it is well-tested and does NOT cause any failure in actual operation, just a performance decrease compared to the more expensive 980.

    7. Re:has not answered the important question by ihtoit · · Score: 1

      uh, the fucking slashdot thread from yesterday?

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    8. Re:has not answered the important question by ihtoit · · Score: 1

      credible citations required. As in, direct links to pages in motherboard manuals that do NOT specify ECC memory modules.

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    9. Re:has not answered the important question by JustNiz · · Score: 1

      Stop trying to change the subject. The issue here is graphics cards and your claims that the 970 is causing crashes. I say prove it.

    10. Re:has not answered the important question by JustNiz · · Score: 1

      The only graphics-related article posted yesterday that I'm seeing is about openCL on Linux.

    11. Re:has not answered the important question by Anonymous Coward · · Score: 0

      actually, it does work exactly like that... the memory controller reads the JEDEC timings, and the system is initialized to the lowest common denominator. technically they could run mis-matched, without any ill effect if there are multiple independent clock sources for the memory system. if you are experiencing crashes, that's a sign of some other issue...

    12. Re:has not answered the important question by jones_supa · · Score: 1

      With "crash out" he possibly didn't mean the whole card crashing, but the memory performance "crashing to lower numbers".

    13. Re:has not answered the important question by jones_supa · · Score: 1

      He probably means the NVIDIA Responds To GTX 970 Memory Bug discussion, although that is indeed a bit older than from yesterday.

    14. Re:has not answered the important question by JustNiz · · Score: 1

      ...Which again makes no mention at all of crashes occuring as he stated several times.
      Seems he's just trolling with no actual evidence. Probably just another rabid ATI fanboi.

    15. Re:has not answered the important question by JustNiz · · Score: 1

      possibly but if so its still a stupid thing to say as its obviously going to confuse meaning.

    16. Re:has not answered the important question by jones_supa · · Score: 1

      True.

  5. Consumers? No just whiny fanboys by Sycraft-fu · · Score: 3, Insightful

    Consumers are fine. The only benchmark that matters to a normal consumer is "How fast does it run my games?" and the answer for the 970 is "Extremely damn fast." It offers performance quite near the 980, for most games so fast that your monitor's refresh rate is the limit, and does so at half the cost. It is an extremely good buy, and I say this as someone who bought a 980 (because I always want the highest end toy).

    Some people on forums are trying to make hay about this because they like to whine, but if you STFU and load up a game the thing is just great. While I agree companies need to keep their specs correct, the idea that this is some massive consumer issue is silly. The spec heads on forums are being outraged because they like to do that, regular consumers are playing their games happily, amazed at how much power $340 gets you these days.

    1. Re:Consumers? No just whiny fanboys by alvinrod · · Score: 3, Insightful

      While that's a reasonable argument (and true) there are some people who do have cause to complain if they would have changed their purchasing decision based on having the correct information at the time of their purchase.

      Honestly, even something like that 970 is overkill for me. I've still got an 8800 in my old machine that runs plenty of games just fine, especially many of the older ones that I'm finally getting around to playing.

    2. Re:Consumers? No just whiny fanboys by JustNiz · · Score: 1

      >> there are some people who do have cause to complain if they would have changed their purchasing decision based on having the correct information at the time of their purchase.

      While I agree that nVidia should have got the published details correct, do you seriously think a customer exists that would not have bought this card had they knew the memory handling strategy was slightly different than published, even though the overall performance of the card was advertised correctly?

      That would be as insane as basing a car purchasing decision entirely on the colour of plastic used for the radiator cap.

    3. Re:Consumers? No just whiny fanboys by Anonymous Coward · · Score: 0

      Nobody has mentioned that the card is really a 224-bit card 99% of the time!

    4. Re:Consumers? No just whiny fanboys by Anonymous Coward · · Score: 0

      You need to work on your car analogies. It's more like finding your 500HP V10 has two spark plugs that only fire half the time.

    5. Re:Consumers? No just whiny fanboys by dissy · · Score: 1

      As an owner of a GTX 970 card, all I can say is I can run Shadow of Mordor at full 1920x1080 res with the "ultra" texture setting and it never dips below 30fps, usually getting 45-60.

      The additional fact I got the card as an open-box return at the local computer store for $220 makes things a no-brainer for me even if the allegations of 3.5gb vram were true.

      There is no game in existence that a 980 or titan card can play that my 970 couldn't, even if I had to bump the settings down to just "very high".

      If I bought a thousand of the things for super computer style multi-GPU number crunching, then I would probably be more upset and yelling a bit louder at Nvidia.
      As a gamer I just can't see myself getting any worked up over this.

    6. Re:Consumers? No just whiny fanboys by Anonymous Coward · · Score: 0

      False advertising is false advertising.

      Belkin/Linksys just wnet through this with WRT1900ac - and offered to directly buy back the units and stores took returns with no questions.

      NVIDIA should setup to the plate and make it right. If you bought 970 with 64 ROP and it only has 56, then fix it.

    7. Re:Consumers? No just whiny fanboys by Anonymous Coward · · Score: 1

      I spent $800 on a pair of 970s and as I use massive resolutions, I use a lot of gram. They basically fucked me and took the cash. This is not what I expect having come from a pair of actual 4gb 670s. So fuck you. I am not a whiny fanboy, I am a pissed CUSTOMER who paid good fucking cash and lots of it.

    8. Re:Consumers? No just whiny fanboys by Anonymous Coward · · Score: 0

      1920 is not a taxing resolution.

      Go 2560x1600 or higher and aim for high frame rates of 80 to 100 or more and you will consume shitloads of bram in many cases.. And encounter this problem.

    9. Re:Consumers? No just whiny fanboys by maorb · · Score: 1

      False advertising requires that the false information, amongst other things, would have affected the purchase decision and resulted in some sort of lose -- usually the amount spent on the item that would otherwise have been used differently.

      So given that requirement I'll go ahead and fix your statement.

      If you bought 970 because it has 64 ROP and it only has 56, then fix it.

    10. Re: Consumers? No just whiny fanboys by Anonymous Coward · · Score: 0

      Yep, and 1080 vertical is a joke -- Sounds like the GP is using a TV for a monitor like I was doing 30 years ago on a TRS-80.

    11. Re:Consumers? No just whiny fanboys by Kjella · · Score: 1

      Hey, I'm still happy about my purchase but when I bought it I looked at the specs and thought: Hmm, they've disabled 3/16ths of the shaders, but it has the same ROPs, same cache, same RAM... if I buy two for SLI it should perform like the GTX 980 except for having 2x13 = 26 shader blocks instead of 16/32 for a single/double 980. Now I find out that's just not true, it has 0.5 GB quasi-RAM it can't access at the listed memory bandwidth, I feel I got very legitimate reason to feel cheated.

      Apparently the ROP/cache isn't a big deal at it makes sense to use 7/8th = 14/16th to serve 13/16th the shaders, if only they'd listed the specs right. But gaming at 3840x2160 with SLI there's a fair chance I could run into a game now or in the future that wants to use all 4GB where it'll either act like a 3.5GB card or drop the framerate significantly underperforming compared to the GTX 980, I don't think that's just theoretical.

      I'd probably still be quite cool with a 3.5GB card with 0.5GB of "last resort" memory that's still faster/lower latency than system memory. But they were in error and have admitted they were in error, I think that goes a little beyond "We said we're sorry" Paying some kind of compensation for falsely promised functionality would not be unreasonable (or swapping my GTX 970s with a 8-channel memory version, but I guess that's overkill). I'd be very surprised if there isn't a class action lawsuit very soon.

      --
      Live today, because you never know what tomorrow brings
    12. Re:Consumers? No just whiny fanboys by Luckyo · · Score: 1

      The issue here is that you're playing on lower resolutions that generally require a lot less VRAM.

      But for that very reason, you don't buy a ~350EUR card for a 1080p. You buy a 200EUR one, which is 960.

      970 is meant for 1440p or higher, and there, and games like SoM start to ask for more VRAM on ultra. A lot more. And at 2160p you're looking at being capped, though for that you'd probably want a 980.

    13. Re: Consumers? No just whiny fanboys by Anonymous Coward · · Score: 0

      Wow, you had a 1080p TV 30 years ago!!!!

    14. Re: Consumers? No just whiny fanboys by Anonymous Coward · · Score: 0

      Great example ... If it makes 500 HP, and meets all other requirements, why should I care about the implementation?

    15. Re:Consumers? No just whiny fanboys by grahamtriggs · · Score: 1

      Kind of.

      You're right, the performance - as long as it stays within 3.5GB - is fine. The thing is, given that the extra 0.5GB brings the performance down, they probably should have just made it a 3GB card - which again would have given the same amount of performance in the majority of cases - and shaved a bit of the costs.

  6. 1/7th the speed? by Anonymous Coward · · Score: 0

    Doesn't this imply that the 500 megabytes of RAM is faster? by a factor of 7?

    1. Re:1/7th the speed? by Orestesx · · Score: 4, Insightful

      This coward has just clearly demonstrated that there is in fact such a thing as a dumb question.

    2. Re:1/7th the speed? by jones_supa · · Score: 1

      The factor is 1/7.

      Use this formula: 1/7 * speed

  7. Better article by gman003 · · Score: 5, Informative

    As usual, AnandTech's article is generally the best technical reporting on the matter

    Key takeaways (aka tl;dr version):
    * Nvidia's initial announcement of the specs was wrong, but only because the technical marketing team wasn't notified that you could partially disable a ROP unit with the new architecture. They overstated the number of ROPs by 8 (was 64, actually 56) and the amount of L2 cache by 256KB (was 2MB, actually 1.75MB). This was quite unlikely to be a deliberate deception, and was most likely an honest mistake.
    * The card effectively has two performance cliffs for exceeding memory usage. Go over 3.5GB, and it drops from 196GB/s to 28GB/s; go over 4GB and it drops from 28GB/s to 16GB/s as it goes out to main memory. This makes it act more like a 3.5GB card in many ways, but the performance penalty isn't quite as steep, and it intelligently prioritizes which data to put in the slower segment.
    * The segmented memory is not new; Nvidia previously used it with the 660 and 660 Ti, although for a different reason.
    * Because, even with the reduced bandwidth, the card is bottlenecked elsewhere, this is unlikely to cause actual performance issues in real-world cases. The only things that currently show it are artificial benchmarks that specifically test memory bandwidth, and most of those were written specifically to test this card.
    * As always, the only numbers that matter for buying a video card are benchmarks and prices. I'm a bigger specs nerd than most, but even I recognize that the thing that matters is application performance, not theoretical. And the application performance is good enough for the price that I'd still buy one, if I were in the market for a high-end but not top-end card.

    Not a shill or fanboy for Nvidia - I use and recommend both companies' cards, depending on the situation.

    1. Re:Better article by rahvin112 · · Score: 1

      Unlikely to be deliberate? For this to NOT be deliberate you have to assume that everyone involved in the design never ever looked at the marketing material, which is absurd. Not only that but even after the card was released the incorrect information was what the company said was the facts until there was objective proof that it was a lie.

      Of course none of this would be a big deal at all had they not lied about it. I'm a long time nvidia user (I don't consider myself a fanboi), but the only way you can say this was an honest mistake is to assume that the marketing people are the only people that get to see the published specs. This was a decision made by high up in the company and it was to deliberately lie.

      This should not be brushed off a "mistake", it was deliberate.

    2. Re:Better article by Xenx · · Score: 1

      Believe it or not, it's quite easy for humans to make mistakes. That isn't to say it definitely was a mistake, but without proof it was intentional we should only take their word it wasn't. This also doesn't absolve them of the mistake. Regardless of intent, it's false advertising.

    3. Re:Better article by gman003 · · Score: 2

      This wasn't "marketing material", it was "technical marketing material", the stuff given to review sites, not the general public. And it was a relatively obscure portion that was incorrect, not something that most consumers would even understand, let alone care about. The technical marketing staff (a distinct group from the consumer marketing department) made the assumption that every enabled ROP/MC functional unit has two 8px/clock ROPs, two L2 cache units of 256KB, two links into the memory crossbar, and two 32-bit memory controllers.

      This assumption was true for previous architectures (Tesla, Fermi, Kepler). It was true for earlier releases in this architecture (the 750 Ti and 980 were full-die releases, no disabled units; the 750 only disabled full units). This is the first architecture where disabling parts of the ROP/MC functional unit, while keeping other parts active, was possible. The marketing department was informed that there were still 8 ROP/MC units, and that there was still a 256-bit memory buss. They were not informed that one ROP/MC unit was partially disabled, with only one ROP and one L2 cache unit, and only one port into the memory crossbar, but still two MCs.

      The point AT made is this: this information would have been figured out eventually. If Nvidia had been up-front with it, it would have been a minor footnote on the universally-positive launch reviews, not dedicated articles just for this issue. It only hurts them to have it not be known information from the get-go.

      As much as it's hip to hate on big corporations for being evil, they are not evil for no purpose. They do evil only when it is more profitable. In this case, the supposed lie was less profitable than the truth. Therefore it was incompetence, either "they honestly didn't know this was how it worked when they sent the info to reviewers", or "they thought they could get away with something that absolutely would have gotten out, and would not help them sell cards anyway". The former incompetence seems far, far more likely than the latter.

    4. Re:Better article by rahvin112 · · Score: 1

      How the information was disseminated and to who is a red herring.

      Technical information was published publicly. No matter how esoteric and incomprehensible it was or how small of an audience it received it was out there and the ONLY way you could argue this is a genuine mistake (in that it remained uncorrected until now) is if the people who inside nvidia who knew the actual capabilities never saw this published public information. I find the idea that their team, who knew it was false, didn't see this published information to be nearly impossible.

      And once you draw the conclusion that there is no way this information wasn't seen by people with the knowledge to know it was false the only conclusion that you can draw is that the decision was made to deliberately ignore that it's false.

      As you say, it's so esoteric of information that for the most part it's irrelevant until you realize they lied about it and did so deliberately (at least by not correcting it). I have difficulty reconciling the idea that this information was so irrelevant when they had to know it was wrong (at the very least after publication someone in nvidia would have saw it) and then still didn't bother to correct it. If the information had been as irrelevant as you claim then such a correction to issued to the sites that published the wrong information would have been a non-event that no one would have cared about. So why not issue the correction?

      My problem isn't with the information, this is a legitimate compromise in the design of a cheaper part. My problem is with the deception. I believe with certainty that someone with knowledge at nvidia saw the wrong information and communicated to those in charge that it was wrong, yet nothing was done and that information has been live until someone validated it as false with benchmarks.

    5. Re:Better article by Mikawo · · Score: 1

      I still have to criticize Nvidia. I don't know if this has been done before on previous cards or not (which doesn't make it ok), but when you advertise a certain amount of memory with no indication that part of that memory performs differently/worse, then that's just wrong.

      Would it be okay if 0.5GB of the 4GB was the pool that actually ran at full speed? I mean technically you still get 4GB... no sane person would say yes. It's not much different than what is happening with the GTX 970 and I think Nvidia should totally be accountable for it.

    6. Re:Better article by Em+Adespoton · · Score: 1

      Yeah; in this case, the initial mistake at publishing appears to be an honest mistake. As the specs lined up and the tech marketing guys were told that nothing changed on that hardware, they kept the same ROP specs they''d already been using in their marketing materials.

      I have to admit that back when I was publishing specs like these, I made that mistake myself a few times.

      However, it's what happened next that's a bit odd: I find it difficult to believe that it took 4 months for it to come to the attention of the company -- and it came from an external source. There's usually some engineer that spends a lot of time reading slashdot and looking up the specs of the products he's worked on -- and they'd likely flag it up. I'd expect 2-month turn-around until the company management realized the mistake.

      The next bit that often happens is asking engineering "Is the change significant in any way?" to which the answer is "no." So marketing is either not even told of the mistake, or told that it's there, but not worth updating the documentation or issuing any sort of an update.

      I find it really odd that they didn't even bother to change it on the website and queue it up for the next round of distribution.

      What this really makes me wonder though, is how often this happens with products held to this standard, and nobody notices....

    7. Re:Better article by Anonymous Coward · · Score: 0

      The problem is, if the opposite were true, where 0.5gb worked at full speed and the rest didn't, it would be seen in benchmarks. Fact of the matter is, the performance hit is small (the 970 is the crippled version anyway). You can read up all the specs but how they actually translate into performance has no bearing whatsoever. So, again, the card hasn't slowed down as a result, because everyone that benchmarked them, did so under the current situation.

    8. Re:Better article by drolli · · Score: 1

      I would imagine that it get most troublesome only if you use the card for computing and rely on a homogenous memory access....

    9. Re:Better article by gman003 · · Score: 1

      I won't make any assumptions about you, but I've *never* looked at the marketing for the product I work on. I don't check to make sure their numbers are accurate, because my job is to build the damn thing, not proofread. If someone from marketing *asks* me to check something, I will, but I don't go around reading reviews to make sure all the numbers are right.

      Further, it's a compromise in a part that's already compromised. In any video card, there are several parts that need to be roughly proportionate in power - memory bandwidth, ROP units, shader units, at the most basic level. Adding extras of any one part won't speed things up, it'll just bottleneck on the other parts. The 980 was a balanced design, perhaps a bit shader-heavy. The 970 took the 980 chip, binned out about 20% of the shaders, binned out about 13% of the ROPs and slowed down one of the memory controllers by segmenting it off. The part that you're complaining is "compromised" is still *over*-engineered for the job at hand. They could have completely removed that memory controller and still been bottlenecked on shaders, not bandwidth.

      Finally, you missed the most crucial part. You are assuming malice, and ignoring any possibility of incompetence, despite it being a very pointless issue to lie about, and very easy to mess up on. In fact, you seem to be ignoring all evidence that it *was* incompetence, and blindly assert that it was malice for no other reason than that you want it to be malice.

    10. Re:Better article by gman003 · · Score: 1

      ... and if you actually have completely random memory access, and if you're using a 970 instead of an actual compute card from the Quadro or Tesla line...

    11. Re:Better article by Anonymous Coward · · Score: 0

      Segmented memory was used in the lower range *60 cards. Not the *70 or 80. We don't expect these shit corner cuttings.

    12. Re:Better article by Anonymous Coward · · Score: 0

      isn't there a reduced/harvested/recovered/disabled card with a tahiti (384b full interface) that only uses 256b? do they have sufficient internal crossbar bandwidth to not starve internal clients (ROP/TEX/ALU) that would otherwise have been connected to the disabled memory controller? if not, OMG they're ripping us off...!!!

      similarly, i have a wekiva chip with an unused sideport... i totally only got that for awesome chip-to-chip awesomeness. again, ripped off...!!!

      the nerdrage is really sad on this topic.

    13. Re:Better article by drolli · · Score: 1

      Yes. I think if I do SW development, a price difference of 3 man-hours of less does not justify the trouble...

  8. Would "incorrectly reported" = false advertising? by Anonymous Coward · · Score: 0

    How far did Nvidia push their performance #s into the public eye before this debacle? Will owners be due a replacement card that preforms up to what was promised or perhaps even a refund?

  9. Car Analogy by QuantumPion · · Score: 1, Insightful

    A particular high performance car has a premium 8 cylinder engine and 32 valves at 400 hp. They also sell a non-premium version which is also 8 cylinders but only 30 valves and makes 350 hp but is a lot cheaper. The difference is that one cylinder is missing two valves which lowers its maximum power compared to the premium version. The engine's computer correctly controls the engine to compensate for the one weird cylinder, but someone in the marketing department sold the car as having 32 valves when it only had 30. The 350 hp figure is accurate, but some people complain because if they reprogram the engine control chip to force the one 2-valve cylinder to run at the same conditions as the other 4-valve cylinders, the car only makes 300 hp. But in all normal circumstances the car performs as advertised, only it was initially sold with incorrect details as to how the engine was put together to make it nearly as fast for much cheaper than the premium version.

    1. Re:Car Analogy by mandark1967 · · Score: 0

      That's a REALLY bad car analogy.

      It's more like:

      Chevy makes a Z-28 Camaro with a 5.7L 525HP V8 engine and sell it as such, with all sales brochures and commercials stating it has a 5.7l 525HP V-8 engine.

      They also make a Base model Camaro with a 5 liter V8 making 450HP.

      Both models hit their estimated performance targets and all performance testing results show the Z-28 out-performs the base model by the pre-determined percentage. As it should.

      Chevy dealers around the nation receive and start selling base models with window stickers stating the base model has a 5.7L 525HP V8 engine. They also receive sales brochures and marketing info stating the same thing.

      They sell the cars for 5 months, and someone finally decides to dyno test the base model. They discover it's only putting out 450HP. (As it was designed to do)

      Chevy figures out what happened and comes back with an ad in Motor Trend stating, "Oops! Bob forgot to update the specs with the marketing department. sry, LOL. It's operating as intended so suck a fat one and get off my jock, kthnx!"

      That's essentially what happened here.

      --
      Sig Follows: "Suppose you were an idiot. And suppose you were a member of Congress. But I repeat myself." -- Mark Twain
    2. Re:Car Analogy by Anonymous Coward · · Score: 0

      Your analogy has a flaw: Everyone already knew the 970 was crippled relative to the 980, so no one ever believed it was a full 5.7L/525HP. Furthermore, every single review posted real life application times (quarter mile maybe?), so everyone got the exact same performance they were promised. Maybe if you said they advertised it as a 5.2L 475HP or something it would be closer.

      Still, I think QuantumPion's analogy was actually okay.

    3. Re:Car Analogy by JustNiz · · Score: 1

      >> window stickers stating the base model has a 5.7L 525HP V8 engine....They discover it's only putting out 450HP

      Not at all, Nvidia has never advertised it as having more performance than it actually has.

    4. Re:Car Analogy by Anonymous Coward · · Score: 0

      But did the specifications point out that it deviates from the reasonable expectation that all of its memory run the same speed?

    5. Re:Car Analogy by Anonymous Coward · · Score: 0

      You seem like someone whose knowledge of how cars work comes from the internet and marketing material. That was so disturbingly misguided.

    6. Re:Car Analogy by Anonymous Coward · · Score: 0

      so run the memory (DRAM) clock slow enough that the chip IOs become the bottleneck, rather than the shared L2 between 2 of the 32b DRAM interfaces. it's all running at the same speed now (and overall perf sucks). thinking about this scenario, you're right, this is a very reasonable expectation. stupid nvida...

    7. Re:Car Analogy by gman003 · · Score: 2

      Both of you suck at car analogies.

      Let's say Nissan makes an engine. V6, 3.8L. They advertize it as being 250HP, promote it mainly by putting it in racecars and winning races, and a whole lot of other technical specs get handed out to reviewers to gush over, but nobody really reads them except nerds.

      They then make a variant engine. Same V6, but they cut the stroke down so it's only 3.0L. They advertize it as being 200HP, promote it with some more racecars that don't win the overall race but are best in their class, and again they hand out a small book worth of technical specs, this one with a minor error in the air flow rates on page 394. Somebody forgot to edit the numbers from the 3.8L engine, so even though the actual airflow is more than enough for the smaller engine, the numbers originally given look bigger. Nobody from marketing was told about the airflow change, because it was a weird side-effect of something they got rid of related to turbocharger compatibility, and nobody thought to ask the engineers to double-check all of their numbers since only like 200 people would see it worldwide anyways.

      Once actual customers get their hands on the new engine, most of them are pretty happy. The 3.8L is better, but it costs like twice as much as the 3.0L, so whatever. One customer is driving on this godawful, decrepit highway that hasn't been repaved since the Eisenhower administration built it, and obviously has some issues. Rather than blame the shitty conditions, he takes a look at the engine, and finds that if you take an air compressor and blow air through the intakes, not as much gets to the engine as in the 3.8L. He then bitches about it online, and other people find the same thing. Motorheads being just as collectively retarded as any group, they build a standardized test set that completely ignores realistic driving conditions and pretty much only identifies this particular oddity in this particular engine, and take to the streets waving torches and pitchforks when they find the air flow value on page 394 isn't the airflow they're getting.

      Someone at Nissan hears the noise outside, checks with their internal books and finds the typo. They start explaining as quickly and loudly as they can, but the mob's angry and nobody's going to stop it with logic at this point.

      Meanwhile, the smart motorheads are sitting back, waiting for Nissan to drop the price on the "tainted" engine so they can pick one up for cheap themselves, since it's actually a perfectly fine engine, already a pretty good one for the price, and way more fuel-efficient than Audi's equivalent.

    8. Re:Car Analogy by Anonymous Coward · · Score: 0

      I think this is not true. There are multiple dimensions to performance: Compute Throughput, Memory Bandwidth, Memory Size, Cache Size. NVidia advertised GTX970 to be different in terms of Compute Throughput, but equal in regards to memory bandwidth, size and cache. But this is clearly not the case. The effective memory interface width of the GTX970 is 224-bit instead of 256-bit, the cache is 1.75MB instead of 2 MB and while technically 4 GB are available, only 3.5 GB are useable at the expected performance.

      I do not think this was a mistake or something NVidia had to do because they deactivated those SMMs in GTX970, but it was done because GTX970 would had likely been too close to GTX980 in performance.

    9. Re:Car Analogy by Carewolf · · Score: 1

      Both of you suck at car analogies.

      Let's say Nissan makes an engine. V6, 3.8L. They advertize it as being 250HP, promote it mainly by putting it in racecars and winning races, and a whole lot of other technical specs get handed out to reviewers to gush over, but nobody really reads them except nerds.

      They then make a variant engine. Same V6, but they cut the stroke down so it's only 3.0L. They advertize it as being 200HP, promote it with some more racecars that don't win the overall race but are best in their class, and again they hand out a small book worth of technical specs, this one with a minor error in the air flow rates on page 394. Somebody forgot to edit the numbers from the 3.8L engine, so even though the actual airflow is more than enough for the smaller engine, the numbers originally given look bigger.

      Except memory for whatever reason is what most laymen measure graphicscard performance on. So it i s not an obscure little number. This is claiming the engine is 3.8L and forgetting to say that it a 3.8L that has been cut to only use 3.0L and therefore perform as a 3.0L.

  10. Re:Would "incorrectly reported" = false advertisin by meerling · · Score: 1

    If consumers end up getting anything, at best it'll probably be an old game download 3 years from now. Those kinds of lawsuits or corporate "apologies" never seem to be worth it, and yet an old game is still far better than most of them, just look at Sony's "apologies" to it's users.

  11. What "fire from consumers"? by Anonymous Coward · · Score: 1

    I just bought a GTX970 and I'm chuffed with it, 89% of the performance of a GTX980 for 60% of the price, I couldn't justify spending the thick end of five hundred quid for a graphics card and the GTX970 will run pretty much anything I throw at it.

    Captcha : illusion

  12. Just give the money back or get more shit by Anonymous Coward · · Score: 0

    NVidia has only one option out of this hole, they need to give a full refund when one returns the card. This is just false advertising and I can truely say, that I will never buy a NVidia, thanks to this and the previous case with defective GPUs which plagued laptops. Two of my friends have met those defective NVidia GPUs, when their a 2-3 year old laptops suddenly lose a GPU, and on both cases the vendor (HP and Acer) has refused to give any compensation.

  13. Just bought two of these cards by xtal · · Score: 1

    I thought about shelling out the dough for the 980s, but didn't, because, well - same CPU, lower clock, right?

    Wrong.

    Less than happy about this.

    --
    ..don't panic
    1. Re:Just bought two of these cards by JustNiz · · Score: 1

      >> Less than happy about this.

      Why? How does it adversely affect you in the real world? You're stil getting the same GPU performance you paid for right?

    2. Re:Just bought two of these cards by xtal · · Score: 1

      I run three 30" 2650x1600s and fully intend on maxing out the VRAM on those cards.

      I get a big hit in doing so. Boo.

      Looking into returning them on principle and getting the 980s.. not sure if that hurts nVidia any, but might piss off their vendors a bit.

      --
      ..don't panic
    3. Re:Just bought two of these cards by JustNiz · · Score: 5, Informative

      >> I run three 30" 2650x1600s
      Thats pretty much irrelevant. GPU ram isn't used that way at all. Its used to hold the 3D geometry, bitmaps, bump maps etc of assets and other processing data which is largely if not completely independent of screen resolution/no.of screens.

      Do the math:
      2560 x 1600 x 4 (4 bytes per pixel for 32 bit color) = 15.625 Mb * 3 monitors = screen buffer for 3 screens total size = 46.875 Mb.

      Even triple buffering your total screen buffer requirement for all 3 monitors is less than 150Mb.

    4. Re:Just bought two of these cards by Yunzil · · Score: 2

      Yeah, you return those cards and give nvidia more money for the more expensive cards. That'll show 'em!

    5. Re:Just bought two of these cards by gman003 · · Score: 1

      ... except they WEREN'T the "same CPU". They were the same GPU die (GM204), but three of the sixteen cores were disabled. This was perfectly explained at launch. If you bought a 970 thinking you could overclock it to 980 clocks and get the exact same performance, I'm sorry, but you just weren't paying any attention.

    6. Re:Just bought two of these cards by Anonymous Coward · · Score: 0

      Good, now do the math for when you aren't just sitting idle at the desktop, such as doing a render in 3ds Max or a massive scene in Poser. Don't make assumptions about other people's usage of hardware.

    7. Re:Just bought two of these cards by Anonymous Coward · · Score: 0

      Yea, you just calculated for ONE FRAME.

      Now please calculate for 60 or more per second, with and without triple buffering.

    8. Re:Just bought two of these cards by Anonymous Coward · · Score: 0

      actually, he calculated 3 frames. Isn't it a good thing that each frame can be dropped after it's used and no longer needed, being overwritten by new data. So teh amount of memory needed is... exactly the same, dumbass.

    9. Re:Just bought two of these cards by Anonymous Coward · · Score: 0

      The framebuffer still accounts for only a small amount of memory usage in most cases.

    10. Re:Just bought two of these cards by Anonymous Coward · · Score: 0

      Z buffers, stencil buffers, off-screen buffers. Your various render buffers can easily climb over 1 gig when there are any FX going on.

    11. Re:Just bought two of these cards by Anonymous Coward · · Score: 0

      then why does resolution affect GPU performance so much?

    12. Re:Just bought two of these cards by jones_supa · · Score: 1

      Because the GPU still has to rasterize all the pixels.

    13. Re:Just bought two of these cards by Anonymous Coward · · Score: 0

      "Good, now do the math for when you aren't just sitting idle at the desktop, such as doing a render in 3ds Max or a massive scene in Poser. Don't make assumptions about other people's usage of hardware."

      The frame buffer memory usage remains the same. Regardless of what you are displaying.

      "Yea, you just calculated for ONE FRAME.
      Now please calculate for 60 or more per second, with and without triple buffering."

      The frame buffer memory usage remains the same. Regardless of the frame rate.

      You people clearly have no idea what a frame buffer does.

    14. Re:Just bought two of these cards by Kjella · · Score: 1

      Thats pretty much irrelevant. GPU ram isn't used that way at all. Its used to hold the 3D geometry, bitmaps, bump maps etc of assets and other processing data which is largely if not completely independent of screen resolution/no.of screens.

      For real-time rendering of a simulated environment - that is, gaming - textures are generally stored as mipmaps so the more pixels it's going to take up on the screen, the more detailed version of the texture is used and thus the memory use rises accordingly through the entire pipeline. It's pretty easy to see if you keep resolution or texture quality constant and vary the other. If you're doing some other kind of simulation that might not hold, but for gaming what you said is pretty much false.

      --
      Live today, because you never know what tomorrow brings
    15. Re:Just bought two of these cards by JustNiz · · Score: 1

      >> You people clearly have no idea what a frame buffer does.

      They're probably the same people that also think buying/adding more ram speeds the processor up.

    16. Re:Just bought two of these cards by JustNiz · · Score: 1

      Yeah I know. Its basicaily what I meant when I listed bitmaps.

      The whole point of using mipmaps is as a strategy to reduce GPU memory/bandwidth usage. Consequently I don't think differentiating between bitmaps and mipmaps is actually relevant to the larger discussion here.

  14. First it's the games, now the hardware :D by nehumanuscrede · · Score: 1

    The reason you don't go out and buy the latest AAA title is because, in recent years, they haven't been living up to the hype. Buggy, unfinished, and not quite the product that is expected. ( You know . . . . playable. )

    Wondering if we have to start doing the same thing with hardware now. Let the same folks who pre-order game titles beta-test this stuff for a few months to determine if the marketing claims are legitimate or not, then decide on if you should buy it.

    " Just ship the damn thing ! We'll update the drivers later. " :|

  15. 3.5 GB of memory... by Anonymous Coward · · Score: 0

    sounds like plenty. I have observed some 3D graphics programs can use 3.5 Gigabytes of random access memory as well. Take for example Poser and Octane Render. Octane loads the entire scene (geometry and textures, I think) into the onboard VRAM. All of the games that I play hardly use 700 MB on my old Nvidia Geforce card with 1 GB of 128 bit memory. I could barely fit a simple 3D scene with a high quality figure and clothes into 1 GB of VRAM.

  16. So where's my refund? by Anonymous Coward · · Score: 0

    I paid for a card with 4GB of ram at 1150Mhz. 0.5GB of that ram is at 1150/7 MHz. Clearly they have lied about their specs and have defrauded millions of people.

    1. Re:So where's my refund? by maorb · · Score: 1

      Your statement that the last .5GB is not running at 1150MHz is as factually correct as Nvidia's statement that the card had 64 ROPs...

      The issue isn't with the speed of the RAM, it's with the setup of the connections between the RAM and the GM204 GPU, the entire last 1GB of RAM is accessed using a single L2 interface, while the other six L2 interfaces only handle .5GB each.

      Each of the seven L2 interfaces in the GPU can handle roughly 22GB/s bandwidth to RAM and data in RAM is interleaved between interfaces, so to reach peak bandwidth (~150GB/s) the last L2 interface dedicates its full bandwidth to just its first .5GB of RAM. Otherwise the first six L2 interfaces (3GB VRAM) would spend half their time waiting for the last interface (1GB) to catch up, since it's reading or writing twice as much data, netting us a peak bandwidth of only ~75GB/s total. Only when 3.5GB is already used does the seventh L2 interface start splitting its performance to use the remaining .5GB. Fortunately NVidia is at least competent enough the least bandwidth intensive stuff on that last .5GB so it doesn't slow down the whole system anywhere close to its the worst case scenario would have predicted.

      Source: TFA

    2. Re:So where's my refund? by jones_supa · · Score: 1

      The practical effect is still similar to the last 0.5GB running at 1150/7 MHz.

  17. Isn't this largely a driver issue? by sabbede · · Score: 1

    Shouldn't the driver be responsible for making sure that "slower" data ends up in that half gig? Something besides the frame buffer or textures. I bet that better memory management could completely hide the problem.