Joe DeFuria
Legend
♪Anode said:I am not sure about this approach. 3dmark is made so that it approximates the game performance.
Well, right off the bat, you are wrong.
3DMark is NOT made to approximate game performance, it is made to stress the hardware in a consisent way. There is a significant difference there. And this is the reason why 3DMark is a valuable tool in addition to actual game performance.
We all know that games normally have specific codepaths for specific hardware. Each GPU ( nv/ati ) does certain things a lot better for others. So normally a game dev(with guidance from an IHV) would optimise for these things to get the maximum performance possible.
Disagree.
SOME will, some won't. And you'll have look at a game by game basis to see which developers use mulitple code paths and which ones don't.
Now 3dmark does most of these things in a fixed way (or the dx9 way) and doesnt have a specific codepath. So this in effect makes its performance not correspond with that of what that particular gpu is fully capable off.
NO single benchmark can test "what the GPU is fully capable of". No game, no synthetic test. All that can be done is to test "How capable each GPU is at running this code, using this data set." 3DMark strives for consistency in code and data set.
Should futuremark also use the approach of game devs and have specific codepaths to remove all doubt from everyones mind ?
No, because we can already use games to answer those types of questions. (At least, for the specific games that are benchmarked.) I think FM should stick with their current policy: keep as 100% consistent as possible.