I also not thinking that nvidia is bottelnecks by the rasterizer. I only want to say thaz AMD is also not bottelnecked by raszerizer.
AMD furyx can do 18.000.000 drawcalls in 3dmark test. Each drawcall have 112 polygons. So the polygonoutput from AMD is 2.000.000.000 Polygons each second...
Furyx is not rasterizer bottlenecked. Otherwise the 3dmark DirectX 12 drawcalltest will not run good on AMD Hardware. Nvidia is rasterizer bottlenecked but it's not the rasterizer it self which make the bottleneck, the Problem which nvidia have is that the command processor can't feed enought...
AMD can do a lot to feed there shader by driver. Also i don't think the Problem is in the frontend. The Problem AMD have is the horrible dx11driver which cant pull any drawcalls to the gpu. There are rumors that AMD's driver use only one thread in the CPU. This will also look like frontend...
AMD have a huge amount of shader to fix there lag with the shader feeding. Nvidia dont have much shader. I think this is the Problem of nvidia. A total unbalanced gpu. To much rasterizer which cant be feedet by the command processor and not enough shader to color up the pixel.
Yes its a draw call test. And what is a draw call test? Sending as much Polygons as possible to the gpu! This Polygons have to be RASZERISED! So the draw call test ist also a rasterizer Test!!! If the rasterizer cant handle the huge amount of drawcall you will See realy Bad results!
Drawcall...
But if AMD rasterizer will be bad than why AMD is leading the Overhead test of the 3dmark?
3dmark overhead test is also a pure rasterizer test with a huge polygoneoutput !!!
If furyx is bottelnecked bye rasterizer then the furyx wehre not so good in the 3dmark overhead test, because its a pure polygonoutput test. So what do we See in the overhead test? The furyx beats the Titan x. So the fury x is not rasterizer bottelnecked.
Nvidia have problems with the command...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.