Announcement

Collapse
No announcement yet.

12-Way Radeon Gallium3D GPU Comparison

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by Sidicas View Post
    I'd say it's logical to put memory configurations (VRAM capacity+VRAM Clock+VRAM Bitwidth) of the cards in the labeling.. I don't think brand is necessary as it doesn't really have any relation to performance. So long as you have *ALL* of the big 3 measurements of video card memory (capacity, clock, bitwidth) you have something meaningful.. Without one of them, it really doesn't say anything.. You could have a lot of capacity without any throughput or vice-versa, so if it's going to be done, I hope it's done right..
    That is fair enough; the main reason I have brought up brand is I that I had found it to be the easiest way to distinguish between my Radeon HD 4670 and the others that were available in the past. A more thorough system would of course lend well to better results.

    Comment


    • #12
      Originally posted by bridgman View Post
      I think the issue is that there's no standard way for PTS to obtain this info.
      Yes, it would be nice to have a universal standard way to obtain GPU memory configuration info from *ANY* graphics card.

      You can actually compare AMD vs. nVidia cards on their memory performance based on memory bitwidth and memory clock which is something you can't do with the GPUs themselves without benchmarking because they have different designs.. nVidia has always historically made very high bitwidth cards because their product releases often happen at awkward times, which is whenever the Taiwan fab is able to manufacture the GPUs with a decent yield... AMD has historically delayed their graphics card releases to correspond with new video memory technology so that they don't need to make their cards high bitwidth, which then means more performance for your money and it's easier to get a lot of board manufs. making AMD graphics cards since the board manuf.'s costs are lower.
      Last edited by Sidicas; 11-27-2012, 07:23 PM.

      Comment


      • #13
        Originally posted by Hamish Wilson View Post
        A better than normal article, but I still would suggest you include a bit more information about the specific cards being tested. For instance, the Radeon HD 4670 you used in your test is not the same as the Radeon HD 4670 I am using in my machine, and I doubt the Radeon HD 6450 in the article is the one I recommended to my brothers. Maybe include a mention of the brand used, such as Sapphire, Diamond, MSI, etc...
        The card manufacturer brand doesn't make any difference on performance, it only determines what the warranty support will be like or after market cooling if they make a model that uses something other then the AMD reference design cooler.

        What does make a world of diference on low end cards is the memory type and it's interconnect bit width. On the low to lower mid range cards you will find all combinations of GDDR, GDDR2, GDDR3, GDDR5 64-bit, 128-bit, etc. For a given GPU core, a card with 64-Bit GDDR5 is going to perform about the same as a card with 128-bit GDDR3 as they will have about the same total VRAM bandwidth.

        Now though you will also see the same GPU core being paired up with an absolutely pitiful 64-bit GDDR which no matter what will always be much slower because all the life is being choked out of it by the lack of VRAM bandwidth.

        Rule of thumb on low end dedicated GPUs, never buy anything with less then 128-bit GDDR5. Memory size doesn't matter pretty much at all since these cards wont have the grunt to handle most heavier games that would need allot of vram anyways, but you still want the card to be able to fully stretch it's legs instead of tying an anvil to it's neck..

        Comment


        • #14
          Originally posted by bridgman View Post
          I think the issue is that there's no standard way for PTS to obtain this info.
          Yet this is not a problem the rest of the hardware sites on the internet have, they put up all the info about the card in all of their graphs.

          Also, don't make crap up about there being no way to garner this information, since GPU-Z gets all of this information and more about every type of GPU, there is no reason PTS cannot get this same information.

          Comment


          • #15
            I still would suggest you include a bit more information about the specific cards being tested.

            Comment


            • #16
              Originally posted by Kivada View Post
              Yet this is not a problem the rest of the hardware sites on the internet have, they put up all the info about the card in all of their graphs.

              Also, don't make crap up about there being no way to garner this information, since GPU-Z gets all of this information and more about every type of GPU, there is no reason PTS cannot get this same information.
              Show me any open-source Linux graphics driver that readily exposes all of the details you desire... PTS already reads core/memory clocks for all drivers (except for the Radeon driver since it only exposes the clock information over debugfs instead of sysfs, unless I run PTS as root or remember to chmod the debug directory before testing, it won't show anything) but the drivers aren't exposing anywhere the memory bus width, etc as far as I know.
              Michael Larabel
              http://www.michaellarabel.com/

              Comment


              • #17
                Originally posted by Kivada View Post
                Also, don't make crap up about there being no way to garner this information, since GPU-Z gets all of this information and more about every type of GPU, there is no reason PTS cannot get this same information.
                Please read my post again. I said there was "no *standard* way" to garner the information, not that there was "no way".

                Comment


                • #18
                  Another 7 Radeon "Southern Islands" commits have just hit mesa git master.

                  Comment


                  • #19
                    Originally posted by Michael View Post
                    Show me any open-source Linux graphics driver that readily exposes all of the details you desire... PTS already reads core/memory clocks for all drivers (except for the Radeon driver since it only exposes the clock information over debugfs instead of sysfs, unless I run PTS as root or remember to chmod the debug directory before testing, it won't show anything) but the drivers aren't exposing anywhere the memory bus width, etc as far as I know.
                    At least on Fedora /sys/kernel/debug and its subfolders are readable for everyone.

                    Comment


                    • #20
                      Originally posted by disi View Post
                      At least on Fedora /sys/kernel/debug and its subfolders are readable for everyone.
                      It used to be that way for Ubuntu too, but was changed a few releases ago.
                      Michael Larabel
                      http://www.michaellarabel.com/

                      Comment

                      Working...
                      X