There was a typo in some of the original HD 5850 decks that went out, which I think may have propogated to some press decks.
Or is it maybe that HD5850 should have that wattage if all 1600SPs were enabled on same clock
As many expected HD4800 type relaunch, but poor 40nm yields borked that.
Why is GTX460 1GB slower than here
http://www.guru3d.com/article/geforce-gtx-460-review/18 where the reference card scores 62?
It's a hype thing cause when you look to buy "that card" usually dont go around snooping for other card reviews, and if youre not constantly follow graphics market you'll be quite happy with your buy ... (or maybe really different settings)
Edit: Hey but it has same 62fps @19x12
We look at many different potential configurtions. The two being discussed for Barts were effectively the same (target) cost so they were analysed more closely to establish which way to go.
What makes this chips so large?! It doesn't even support FP64, nor even have 1280SPs, but accordingly it sports somewhat smaller Redwood MC (x2 to become 256-bit, and not supporting differential gddr5 signaling makes him 50% smaller than one in Cypress/Juniper).
So what's the legend behind it? It's not like only one more tessellation dispatcher aka. RPE (what it stands for?) needs to consume enormous die space.
the chip is 80mm sq smaller then cypress hits almost the same performace at the same power on the same node and its only been a year since cpyress came out, how isn't that hitting the mark? remeber that according to dave that the sweet spot card was juniper not cypress and thats why there is the naming confusion right now because evergreen family wasn't named like it should have been.
In fact it's not all so shiny ruby as you can see from above. But they tweaked performance as much as they could on 1120SPs that wont go much further 960MHz almost reaching HD5870 consumption with 60MHz increase. But it's
great enough as gaming solution in ring vs. GTX460 1GB.
All they improved is "broken" AF filtering that shouldn't be broken in first place and MLAA (application) looks like technique we saw 12+ yrs ago with jpeg popularization. So we could at least ask why it aint be there before? It's definetely cheap enough trick that done almost same job as EdgeAA with
"huge improvements" on reducing shader utilization to get job done
"with similar results". At least i hope we'll saw thus MLAA enabled in drivers for HD5000 series and only then we might get better comparison on HD6800 improvements over HD5700/5800, beyond already mentioned second tessellation dispatching coprocessor/unit - RPE.
you/NV should thank there lucky stars that 32nm got canned otherwise that 255mm sq die would be tiny, it actually would have been funny (in a sad way) seeing NV having to price the 470 to compete with it.
Well smaller die space is great for (now) AMD, but that doesnt meant too much for me as consumer because HD5850 on launch had Dirt2 coupon and was selling at 260USD promo price while a year later we get small tesselation+filtering improvements that should be there in first place a year ago. And new DirectCompute application gimmick - MLAA. So all we can hope is that AMD can better reduce prices on Barts than it could on x1.33 larger Cypress.
