AMD Comments on GPU Stuttering, Offers Driver Roadmap & Perspective on Benchmarkingby Ryan Smith on March 26, 2013 2:28 AM EST
For as long as I can remember talking about video cards and GPU performance at AnandTech, there has been debate over the type of benchmarks used to represent that performance. In the old days, the debate was mostly manufacturer driven. Curiously enough, the discourse usually fired up when one manufacturer was at a significant deficit in GPU performance. NVIDIA made a big deal about moving away from timedemos and average frame rates during the early GeForce FX (NV30) days, when its cards might have delivered a decent gaming experience but were slaughtered in most benchmarks. Even Intel advocated for a shift away from most CPU bound gaming benchmarks back during the early years of the Pentium 4 - again, for obvious reasons.
It’s a shame that these revolutions in gaming performance testing were always associated with underperforming products (and later dropped once the product stack improved in the next generation or two). It’s a shame because there has always been merit in introducing additional metrics in order to provide the most complete picture when it came to gaming performance.
The issue lay mostly dormant over the past several years. Every now and then there’d be a new attempt to revolutionize GPU performance testing, but most failed to gain widespread traction for one reason or another. Broad repeatability, one of the basic tenets of the scientific method, was usually cast aside in pursuit of a lot of these new attempts at performance testing - which ultimately limited acceptance.
A year and a half ago, Scott Wasson over at the Tech Report did something no one since Dr. Pabst was able to do: he actually brought about a revolution in the 3D game benchmarking scene.
The approach seemed ridiculously simple - we’ve all had the tools for so very long. Scott used FRAPS to record frame times, and would calculate how long every frame in a benchmark took to render. By focusing on individual frame latencies, Scott’s method could better characterize the little hiccups and stutters that would get smoothed out in an average frame rate. With the new method came a bunch of nifty graphs, and the world changed.
The methodology wasn’t perfect, as FRAPS lacks a holistic view of the 3D rendering pipeline, but it did reveal some surprising issues (in addition to spawning further work that uncovered even more issues on the multi-GPU front). Interestingly enough, many of the issues uncovered by this focus on frame times/latency seemed to primarily impact AMD hardware.
AMD remained curiously quiet as to exactly why its hardware and drivers were so adversely impacted by these new testing methods. While our own foray into evolving GPU testing will come later this week, we had the opportunity to sit down with AMD to understand exactly what’s been going on.
Although neither strictly a defense nor merely an explanation of what we’ve been seeing over the past year, AMD wanted to sit down and better explain their position. This includes both why AMD’s products have been impacted in the manner they were, and why at the same time (and not unlike NVIDIA) AMD is worried about FRAPS being given more weight than it should be. Ultimately AMD believes that it’s to the benefit of buyers and journalists alike to better understand just what is happening, why it’s happening, and just what the most common tools can and are measuring.
What follows is based on our meeting with some of AMD's graphics hardware and driver architects, where they went into depth in all of these issues. In the following pages we’ll get into a high-level explanation of how the Windows rendering pipeline works, why this leads to single-GPU issues, why this leads to multi-GPU issues, and what various tools can measure and see in the rendering process.
Post Your CommentPlease log in or sign up to comment.
View All Comments
maxcellerate - Saturday, March 30, 2013 - linkthey have it's called an 'eyeball', but I doubt it'll catch on.
Sandcat - Tuesday, March 26, 2013 - linkI've read rumors that the Kepler refresh is 'supposed' to be out in Q3 2013. Anyone know how accurate this is?
stickmansam - Tuesday, March 26, 2013 - linkMaybe near the end of the year/holidays is what I am hearing for AMD and Nvidia refresh
hero1 - Tuesday, March 26, 2013 - linkThat's the correct guestimate. I think AMD will be the end of the year/start of 2014 and Nvidia probably end of 3rd quarter/start of 4th quarter since they don't have to make console hardware apart from their own handheld.
EzioAs - Tuesday, March 26, 2013 - linkWasn't it Q4? Anyway, as stickmansam said, it'll probably at the end of the year.
stickmansam - Tuesday, March 26, 2013 - link^ I think I've seen your name around somewhere -.-
EzioAs - Tuesday, March 26, 2013 - linkTHG?
stickmansam - Tuesday, March 26, 2013 - linkYeah that's where :)
Integr8d - Tuesday, March 26, 2013 - linkIn recapping the history, I believe it was around 04' or 05' that ATI and Nvidia were getting busted for optimizing their drivers for the benchmarks. Can't forget that boondoggle!
faizo - Tuesday, March 26, 2013 - linkGreat and very informative article.
Kudos to AMD for admitting to their issues and working on a fix.