By: Kevin G (kevin.delete@this.cubitdesigns.com), April 14, 2011 11:30 am
Room: Moderated Discussions
David Kanter (dkanter@realworldtech.com) on 4/12/11 wrote:
---------------------------
>As many of you may have noticed, we've had a profusion of new articles at RWT in
>the last few months. I have been writing one short article per week, for the last
>5 weeks, while still working on several longer pieces (Poulson, z196, cough cough).
z196? Do tell.
>Without further ado, here's the deal on this weeks article:
>
>Modern graphics processors are incredibly complex, but understanding their performance
>is essential, as they become an increasingly important component of computer systems.
>In this report, we use a set of benchmark results to build accurate performance
>models for AMD and Nvidia GPUs. We verify that our model can predict performance
>within roughly 6-8% for many desktop graphics cards and show how Nvidia’s microarchitecture
>and drivers achieve roughly 2X higher utilization than AMD’s VLIW5 design.
The problem with benchmarks and graphics is that it is very easy to run into some sort of bottleneck. The data points were generated using a 1280 x 1024 resolution to minimize the affect of fill rate and memory bandwidth. Fair point until you start to run into CPU bottlenecks. This may only appear with the high end GPU's but it will skew the results. Similarly bench marking at 1920 x 1080 would produce subpar results for low end GPU's for the reasons previously mentioned. I feel that the best way is basically to run the analysis several times at different resolutions. Perhaps a 3D plot of just nVidia GPU's with the three axis labeled: GFLOP, 3Dmark and megapixel?
Another thing I'd like to have seen would be some love for older graphics cards (Geforce 8800GTX, Radeon 3870 ect.). My real curiosity here with the internal changes between the Radeon 2000, 3000 and 400 lines. While AMD didn't fundamentally chance their VLIW5 shader core during these generations, they modified many other characteristics. The internal ring memory bus of the Radeon 2000 was dropped, the number of TMU's and ROP's increased in efficiency, especially when dealing with anti-aliasing. If the analysis holds up for the modern cards, it should be able to accurately predict the results of the older cards: you don't necessarily have to wait for something new.
---------------------------
>As many of you may have noticed, we've had a profusion of new articles at RWT in
>the last few months. I have been writing one short article per week, for the last
>5 weeks, while still working on several longer pieces (Poulson, z196, cough cough).
z196? Do tell.
>Without further ado, here's the deal on this weeks article:
>
>Modern graphics processors are incredibly complex, but understanding their performance
>is essential, as they become an increasingly important component of computer systems.
>In this report, we use a set of benchmark results to build accurate performance
>models for AMD and Nvidia GPUs. We verify that our model can predict performance
>within roughly 6-8% for many desktop graphics cards and show how Nvidia’s microarchitecture
>and drivers achieve roughly 2X higher utilization than AMD’s VLIW5 design.
The problem with benchmarks and graphics is that it is very easy to run into some sort of bottleneck. The data points were generated using a 1280 x 1024 resolution to minimize the affect of fill rate and memory bandwidth. Fair point until you start to run into CPU bottlenecks. This may only appear with the high end GPU's but it will skew the results. Similarly bench marking at 1920 x 1080 would produce subpar results for low end GPU's for the reasons previously mentioned. I feel that the best way is basically to run the analysis several times at different resolutions. Perhaps a 3D plot of just nVidia GPU's with the three axis labeled: GFLOP, 3Dmark and megapixel?
Another thing I'd like to have seen would be some love for older graphics cards (Geforce 8800GTX, Radeon 3870 ect.). My real curiosity here with the internal changes between the Radeon 2000, 3000 and 400 lines. While AMD didn't fundamentally chance their VLIW5 shader core during these generations, they modified many other characteristics. The internal ring memory bus of the Radeon 2000 was dropped, the number of TMU's and ROP's increased in efficiency, especially when dealing with anti-aliasing. If the analysis holds up for the modern cards, it should be able to accurately predict the results of the older cards: you don't necessarily have to wait for something new.
Topic | Posted By | Date |
---|---|---|
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/11 11:55 PM |
Graph is not red-green colorblind friendly (NT) | RatherNotSay | 2011/04/12 03:51 AM |
Fixed | David Kanter | 2011/04/12 08:46 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | James | 2011/04/12 12:30 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/12 02:51 PM |
Try HD6450 or HD6850 | EduardoS | 2011/04/12 03:31 PM |
Try HD6450 or HD6850 | David Kanter | 2011/04/13 10:25 AM |
Try HD6450 or HD6850 | EduardoS | 2011/04/13 03:20 PM |
of cause | Moritz | 2011/04/14 08:03 AM |
of cause | EduardoS | 2011/04/14 01:55 PM |
Barts = 5D | Moritz | 2011/04/14 09:26 PM |
Barts = 5D | Antti-Ville Tuunainen | 2011/04/15 12:38 AM |
Limiting fixed function units | Moritz | 2011/04/15 04:28 AM |
Limiting fixed function units | Vincent Diepeveen | 2011/04/20 02:38 AM |
lack of detail | Moritz | 2011/04/20 09:24 AM |
lack of detail | EduardoS | 2011/04/20 11:45 AM |
gpgpu | Vincent Diepeveen | 2011/04/16 02:10 AM |
gpgpu | EduardoS | 2011/04/17 12:31 PM |
gpgpu | Groo | 2011/04/17 12:58 PM |
gpgpu | EduardoS | 2011/04/17 01:08 PM |
gpgpu | Ian Ameline | 2011/04/18 03:55 PM |
gpgpu | Ping-Che Chen | 2011/04/19 12:59 AM |
GPU numerical compliance | Sylvain Collange | 2011/04/19 11:38 AM |
GPU numerical compliance | Vincent Diepeveen | 2011/04/20 02:17 AM |
gpgpu | Vincent Diepeveen | 2011/04/20 02:02 AM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 04:41 AM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/20 05:52 AM |
gpgpu and core counts | none | 2011/04/20 07:05 AM |
gpgpu and core counts | EduardoS | 2011/04/20 11:36 AM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 10:16 AM |
gpgpu and core counts | EduardoS | 2011/04/20 11:34 AM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 07:24 PM |
gpgpu and core counts | EduardoS | 2011/04/20 08:55 PM |
gpgpu and core counts | Heikki Kultala | 2011/04/21 06:48 AM |
gpgpu and core counts | EduardoS | 2011/04/22 01:41 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/21 10:42 AM |
AMD Compute and Texture Fetch | Vincent Diepeveen | 2011/04/22 01:14 AM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 10:53 AM |
AMD Compute and Texture Fetch | EduardoS | 2011/04/22 01:46 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 02:02 PM |
AMD Compute and Texture Fetch | EduardoS | 2011/04/22 02:18 PM |
AMD Compute and Texture Fetch | anon | 2011/04/22 03:30 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 09:17 PM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/20 12:12 PM |
gpgpu and core counts | Heikki Kultala | 2011/04/21 10:23 AM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/22 02:11 AM |
Keep the crazy politics out of this | David Kanter | 2011/04/22 08:39 AM |
Keep the crazy politics out of this | Vincent Diepeveen | 2011/04/22 09:12 AM |
Keep the crazy politics out of this | David Kanter | 2011/04/22 10:44 AM |
gpgpu and core counts | Jouni Osmala | 2011/04/22 11:06 AM |
gpgpu | EduardoS | 2011/04/20 11:59 AM |
gpgpu | Vincent Diepeveen | 2011/04/20 12:37 PM |
gpgpu | EduardoS | 2011/04/20 05:27 PM |
gpgpu | Vincent Diepeveen | 2011/04/21 02:06 AM |
gpgpu | EduardoS | 2011/04/22 02:00 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | PiedPiper | 2011/04/12 10:05 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/12 10:42 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | MS | 2011/04/15 05:04 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | Kevin G | 2011/04/16 02:25 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/16 08:42 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | Vincent Diepeveen | 2011/04/20 02:20 AM |
memory | Moritz | 2011/04/14 09:03 PM |
memory - more | Moritz | 2011/04/15 11:11 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | Kevin G | 2011/04/14 11:30 AM |