Announcement

Collapse
No announcement yet.

AMDGPU-PRO vs. Open-Source Gallium3D OpenGL Performance On Polaris Is A Very Tight Race

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

  • #21
    This is excellent stuff, I'm really hopeful for the future for AMD on Linux. Once the supply stabilises I think I'll be getting a 470, that looks like the card for me.

    I've just upgraded my Windows GPU and as a result have a 770gtx lying around but I can't bring myself to put an Nvidia card in my Linux box, it just seems wrong. It amazes me the progress the open source driver has made and I'll stick with the red team on Linux. This article really brings it home what a superb jobs the devs have done on the OS driver.

    Comment


    • #22
      Originally posted by Michael View Post

      As far as I know, CS:GO doesn't expose the frame time information via a parseable way to PTS (e.g. output or file) so unless there are some options I am unaware of, not possible.
      Didn't I read a long time ago that pts could use libframetime for that? Or am I imagining things?

      Comment


      • #23
        Originally posted by haagch View Post
        Didn't I read a long time ago that pts could use libframetime for that? Or am I imagining things?
        I added that support still, but it's less than ideal and has caused issues with some games.
        Michael Larabel
        https://www.michaellarabel.com/

        Comment


        • #24
          Originally posted by haagch View Post
          It's not. The HUD shows zero shaders created and zero compilations while it happens. But just now I noticed that the GTT usage drops a little bit, so I suspect something inefficient somewhere in the memory management. First thought is of course https://lists.freedesktop.org/archiv...st/001360.html but there can be no memory pressure on my 8 gigabyte rx 480...
          Wow, great analysis! I didn't know the HUD was so powerful.

          Comment


          • #25
            Originally posted by Azpegath View Post

            Wow, great analysis! I didn't know the HUD was so powerful.
            It can expose a lot of driver internals. On RX 480:
            Code:
             Available names:
               fps
               cpu
               cpu0
               cpu1
               cpu2
               cpu3
               samples-passed
               primitives-generated
               ia-vertices
               ia-primitives
               vs-invocations
               gs-invocations
               gs-primitives
               clipper-invocations
               clipper-primitives-generated
               ps-invocations
               hs-invocations
               ds-invocations
               cs-invocations
               num-compilations
               num-shaders-created
               draw-calls
               spill-draw-calls
               compute-calls
               spill-compute-calls
               dma-calls
               requested-VRAM
               requested-GTT
               mapped-VRAM
               mapped-GTT
               buffer-wait-time
               num-cs-flushes
               num-bytes-moved
               VRAM-usage
               GTT-usage
               back-buffer-ps-draw-ratio
               GPIN_000
               GPIN_001
               GPIN_002
               GPIN_003
               GPIN_004
               GPU-load
               CB0_000
               ...
               CB3_395
               CPF_000
               ...
               CPF_018
               DB0_000
               ...
               DB3_256
               GRBM_000
               ...
               GRBM_033
               GRBMSE_000
               ...
               GRBMSE_014
               PA_SU_000
               ...
               PA_SU_152
               PA_SC_000
               ...
               PA_SC_396
               SPI_000
               ...
               SPI_196
               SQ_000
               ...
               SQ_CS_272
               SX_000
               ...
               SX_033
               TA0_000
               ...
               TA15_118
               TCA0_000
               ...
               TCA1_034
               TCC0_000
               ...
               TCC15_191
               TD0_000
               ...
               TD15_054
               TCP0_000
               ...
               TCP15_179
               GDS_000
               ...
               GDS_120
               VGT_000
               ...
               VGT_146
               IA_000
               ...
               IA_023
               MC_000
               ...
               MC_021
               SRBM_000
               ...
               SRBM_026
               WD_000
               ...
               WD_036
               CPG_000
               ...
               CPG_047
               CPC_000
               ...
               CPC_023

            Comment


            • #26
              Originally posted by bwyan View Post
              Thanks for the suggestion. I can't seem to find anything related to governor settings for the GPU though. Are You referring to the governor for the CPU?
              Yup, CPU governor performance.

              Comment


              • #27
                what is the point of non free drivers? Amd gain some brains

                Comment


                • #28
                  Originally posted by bwyan View Post
                  I just tried duplicating these results using phoronix-test-suite. For some reason, the AMDGPU-PRO driver always performs much worse for me on my new AMD R9 Fury on Ubuntu 16.04 when comparing my results to the ones Michael are getting (around ~25-30 percent lower). Is there something that I may be missing that I should be aware of or is my GPU simply being bottlenecked by my i5-2500k CPU?
                  For anyone interested, it turned out that my problem was that I had "non-stock" kernels 4.7 and 4.8rc2 installed (for experimentation with Mesa improvements).

                  Even though I had booted on stock 4.4 kernel when installing the amdgpu-pro driver, the amdgpu-pro-installer still attempted to build kernel modules for the newer kernels and threw errors for those. However, the kernel module for kernel 4.4 seemed to be built as expected and so, as glxinfo was reporting OpenGL 4.5 compatibility, I assumed that everything was dandy.

                  In the end, uninstalling kernel 4.7 and 4.8rc2 and then reinstalling the driver seems to have resolved my problems and the amdgpu-pro driver now performs more or less in line with Michael's results.

                  Comment


                  • #29
                    He, he, steamos again get new pro driver... seems every month new blob checkout

                    Comment


                    • #30
                      Nice results for the FOSS driver; if non-overclocked RX 470 appear that need no more than 120W and the driver is improved enough so that games perform better than on a GTX 970, then I may buy one… At the moment I’m looking at getting a GTX 1060 instead because it performs much better, needs no more than 120W and I’m sure the drivers will work very well.

                      It makes no sense that the RX 470 performs just as well or better than the RX 480… It also costs the same… (Yes I know it’s an overclocked RX 470, but still.)

                      Comment

                      Working...
                      X