By: David Kanter (dkanter.delete@this.realworldtech.com), April 12, 2011 11:42 pm
Room: Moderated Discussions
PiedPiper (jamesdgwise@gmail.com) on 4/13/11 wrote:
---------------------------
>Another good article, and i definitely like the idea of more regular smaller, and
>as a result simpler/easier to understand,
>articles.
>
>A good if somewhat basic analysis of modern GPU's.
>I'm interested as to weather or not you did any testing / theorizing that took
>into account memory bandwidth, prior to ignoring that >factor?
Absolutely. I decided that I didn't have the time or word count to really deal with it adequately. Bandwidth matters, but one step at a time.
>I cant help but think *purely guessing though* that if you added a scaling factor
>that accounted for differences in memory bandwidth, that your results might be even
>more accurate, especially when generalizing from the >laptop to the desktop version of the cards.
That's definitely true, and the models I use for myself include memory bandwidth. But as I said in the article - it's more complicated, harder to visualize and really just beyond the scope of what I wanted to do.
>EG. Memory bandwidth / number of processing cores
>( or maybe establish a baseline memory Bandwidth for each >model of GPU, and then compare against that....
>
>Also interested as to why you chose notebookcheck.net as >your data source? Why
>not use Anand/Hardocp/techreport and compare desktop GPU's?
Of the three you mentioned, I only really trust data from Scott @ TR. Unfortunately, Scott doesn't use 3DMark, and I didn't want to use a real game (for a variety of reasons which might become clear later). Moreover, none of them put their data into a form that is readily usable.
>Oh and i would have been interested to see results from the new VLIW4 ati cards,
>even if the are outliers and represent a different >architecture.
There were only 2 data points, which is the bare minimum needed for any sort of analysis. I'm just not very comfortable doing any sort of modeling with that little data. Perhaps in the future though...
David
---------------------------
>Another good article, and i definitely like the idea of more regular smaller, and
>as a result simpler/easier to understand,
>articles.
>
>A good if somewhat basic analysis of modern GPU's.
>I'm interested as to weather or not you did any testing / theorizing that took
>into account memory bandwidth, prior to ignoring that >factor?
Absolutely. I decided that I didn't have the time or word count to really deal with it adequately. Bandwidth matters, but one step at a time.
>I cant help but think *purely guessing though* that if you added a scaling factor
>that accounted for differences in memory bandwidth, that your results might be even
>more accurate, especially when generalizing from the >laptop to the desktop version of the cards.
That's definitely true, and the models I use for myself include memory bandwidth. But as I said in the article - it's more complicated, harder to visualize and really just beyond the scope of what I wanted to do.
>EG. Memory bandwidth / number of processing cores
>( or maybe establish a baseline memory Bandwidth for each >model of GPU, and then compare against that....
>
>Also interested as to why you chose notebookcheck.net as >your data source? Why
>not use Anand/Hardocp/techreport and compare desktop GPU's?
Of the three you mentioned, I only really trust data from Scott @ TR. Unfortunately, Scott doesn't use 3DMark, and I didn't want to use a real game (for a variety of reasons which might become clear later). Moreover, none of them put their data into a form that is readily usable.
>Oh and i would have been interested to see results from the new VLIW4 ati cards,
>even if the are outliers and represent a different >architecture.
There were only 2 data points, which is the bare minimum needed for any sort of analysis. I'm just not very comfortable doing any sort of modeling with that little data. Perhaps in the future though...
David
Topic | Posted By | Date |
---|---|---|
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/12 12:55 AM |
Graph is not red-green colorblind friendly (NT) | RatherNotSay | 2011/04/12 04:51 AM |
Fixed | David Kanter | 2011/04/12 09:46 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | James | 2011/04/12 01:30 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/12 03:51 PM |
Try HD6450 or HD6850 | EduardoS | 2011/04/12 04:31 PM |
Try HD6450 or HD6850 | David Kanter | 2011/04/13 11:25 AM |
Try HD6450 or HD6850 | EduardoS | 2011/04/13 04:20 PM |
of cause | Moritz | 2011/04/14 09:03 AM |
of cause | EduardoS | 2011/04/14 02:55 PM |
Barts = 5D | Moritz | 2011/04/14 10:26 PM |
Barts = 5D | Antti-Ville Tuunainen | 2011/04/15 01:38 AM |
Limiting fixed function units | Moritz | 2011/04/15 05:28 AM |
Limiting fixed function units | Vincent Diepeveen | 2011/04/20 03:38 AM |
lack of detail | Moritz | 2011/04/20 10:24 AM |
lack of detail | EduardoS | 2011/04/20 12:45 PM |
gpgpu | Vincent Diepeveen | 2011/04/16 03:10 AM |
gpgpu | EduardoS | 2011/04/17 01:31 PM |
gpgpu | Groo | 2011/04/17 01:58 PM |
gpgpu | EduardoS | 2011/04/17 02:08 PM |
gpgpu | Ian Ameline | 2011/04/18 04:55 PM |
gpgpu | Ping-Che Chen | 2011/04/19 01:59 AM |
GPU numerical compliance | Sylvain Collange | 2011/04/19 12:38 PM |
GPU numerical compliance | Vincent Diepeveen | 2011/04/20 03:17 AM |
gpgpu | Vincent Diepeveen | 2011/04/20 03:02 AM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 05:41 AM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/20 06:52 AM |
gpgpu and core counts | none | 2011/04/20 08:05 AM |
gpgpu and core counts | EduardoS | 2011/04/20 12:36 PM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 11:16 AM |
gpgpu and core counts | EduardoS | 2011/04/20 12:34 PM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 08:24 PM |
gpgpu and core counts | EduardoS | 2011/04/20 09:55 PM |
gpgpu and core counts | Heikki Kultala | 2011/04/21 07:48 AM |
gpgpu and core counts | EduardoS | 2011/04/22 02:41 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/21 11:42 AM |
AMD Compute and Texture Fetch | Vincent Diepeveen | 2011/04/22 02:14 AM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 11:53 AM |
AMD Compute and Texture Fetch | EduardoS | 2011/04/22 02:46 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 03:02 PM |
AMD Compute and Texture Fetch | EduardoS | 2011/04/22 03:18 PM |
AMD Compute and Texture Fetch | anon | 2011/04/22 04:30 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 10:17 PM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/20 01:12 PM |
gpgpu and core counts | Heikki Kultala | 2011/04/21 11:23 AM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/22 03:11 AM |
Keep the crazy politics out of this | David Kanter | 2011/04/22 09:39 AM |
Keep the crazy politics out of this | Vincent Diepeveen | 2011/04/22 10:12 AM |
Keep the crazy politics out of this | David Kanter | 2011/04/22 11:44 AM |
gpgpu and core counts | Jouni Osmala | 2011/04/22 12:06 PM |
gpgpu | EduardoS | 2011/04/20 12:59 PM |
gpgpu | Vincent Diepeveen | 2011/04/20 01:37 PM |
gpgpu | EduardoS | 2011/04/20 06:27 PM |
gpgpu | Vincent Diepeveen | 2011/04/21 03:06 AM |
gpgpu | EduardoS | 2011/04/22 03:00 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | PiedPiper | 2011/04/12 11:05 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/12 11:42 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | MS | 2011/04/15 06:04 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | Kevin G | 2011/04/16 03:25 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/16 09:42 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | Vincent Diepeveen | 2011/04/20 03:20 AM |
memory | Moritz | 2011/04/14 10:03 PM |
memory - more | Moritz | 2011/04/16 12:11 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | Kevin G | 2011/04/14 12:30 PM |