Nope.... just that one frame shot of an instaneous grab by someone on a keyboard is not reproducible and statistically valid.Originally Posted by gosh
http://www.techreport.com/articles.x/15293/9
This is a time run (via FRAPs) of a race around an entire track.
Take the 4870X2 trace, solid orange for example. Look at the first dip at 79, then eyeball an average (it is actually 94.1) ... a single frame from the anywhere within the run is not representative of what the frame rate actually is for this game.
The data just isn't a valid data set to analyze to any conclusions.
Now notice that the Techreport data shows GRID for a 3.0 GHz 9650 -- again, at high resolution, if this were an issue ... do you think they would getting in the 100's FPS? Doesn't this sorta knock the data you showed out of the water....
Heck, even Techreport's data set can be debated .. why? Because no two traces are the same, the author relies on one lap around the track but it is impossible for a user to reproducibly run the track exactly the same way for ever test case. Examine the lowest trace, at around 75-80 seconds into the race it takes a huge dip and stays flat for 10-15 seconds (he likely crashed and had trouble recovering) and this is factored into his calculation. Thus his framerate for that run is way off.
BTW even these traces are showing normal, random gaming behavior, there is not hint of any bottlnecking... there is good reason for this.
This is kinda fun...
jack
Bookmarks