Announcement

Collapse
No announcement yet.

Announcing radeontop, a tool for viewing the GPU usage

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

  • Announcing radeontop, a tool for viewing the GPU usage

    While the performance counters are still undocumented, at least some monitoring is possible.

    Announcing radeontop v0.5.1. An userspace tool for the open Radeon drivers, supporting R600 and up.




    Comments, bug reports, translations welcome. Package it for your distro if you like
    I'll be setting up launchpad translations if this proves popular.

    Download:
    https://github.com/clbr/radeontop

  • #2
    Coolcoolcool! I've been waiting for something like this!

    Minor nitpick, on my system make didn't generate version.h, I had to run getver.sh manually:
    radeontop.h:22:21: fatal error: version.h: No such file or directory

    I also see that my vertex cache reports 100% usage all the time, not sure what's up with that.

    Comment


    • #3
      Originally posted by whizse View Post
      I also see that my vertex cache reports 100% usage all the time, not sure what's up with that.
      Just a wild guess, but IIRC some of the low end parts didn't have a vertex cache and so vertex fetches went through the texture cache.

      Comment


      • #4
        ?!?

        Good morning
        Great tool, does that look healthy?



        I had problems with getvers.sh btw... for some reason version.h wasn't created, had to do it manually.

        //edit: running
        Code:
        % sh getvers.sh
        works as well
        Last edited by disi; 07-08-2012, 02:26 AM.

        Comment


        • #5
          Thanks for the feedback, I've pushed 0.5.2 which should fix the build issue w/ version.h.

          As for the vertex cache, it seems the bit changed meaning starting with Evergreen, ie you can only see the vertex cache usage on r600 and r700. I'll fix that soon.

          Comment


          • #6
            Removed the VC display, seems it was only valid for r600 if even that. The TC may be wrong too, but hey, working off contradicting docs here

            Comment


            • #7
              Originally posted by curaga View Post
              Removed the VC display, seems it was only valid for r600 if even that. The TC may be wrong too, but hey, working off contradicting docs here
              Hehe, since S.I. were completely reworked I am wondering, works on N.I. though

              Comment


              • #8
                r600_demo claims a bunch of other bits are r600-only, so marked them as such.

                BTW: glxgears only keeps my GPU 70% busy, despite spinning at ~1200fps. Heavier loads do get it to 100%. Clearly a deficiency in the stack

                Comment


                • #9
                  Very cool work!

                  Comment


                  • #10
                    Nice job, been wanting this... (though ideally over debugfs/sysfs...) Is there a dump command so it would dump all of the stats and quit? That way PTS could auto-parse this data while running benchmarks
                    Michael Larabel
                    http://www.michaellarabel.com/

                    Comment


                    • #11
                      Great, this sounds promising!

                      Testing with glxgears running results in this oscillating output:

                      http://www.vidup.de/v/yN2La/

                      Is that expected?
                      Last edited by entropy; 07-08-2012, 09:38 AM.

                      Comment


                      • #12
                        Good job, we need more efforts like this across the board (ie not only GPU monitoring).

                        Now make a qt ui for it and I will award you 3845 brownie points. ;D

                        Comment


                        • #13
                          Originally posted by deanjo View Post
                          Good job, we need more efforts like this across the board (ie not only GPU monitoring).

                          Now make a qt ui for it and I will award you 3845 brownie points. ;D
                          inb4 patches welcome

                          Comment


                          • #14
                            Originally posted by Michael View Post
                            Nice job, been wanting this... (though ideally over debugfs/sysfs...) Is there a dump command so it would dump all of the stats and quit? That way PTS could auto-parse this data while running benchmarks
                            No dump command yet, what kind of interface would you like?

                            It gets the percentage numbers by polling the register the requested times per second. Do you want the percentages after one second, or immediate output (where PTS would itself have to call the app N times per second to get accurate output)?

                            Or maybe it should keep running and just post the raw data for every tick?

                            Testing with glxgears running results in this oscillating output:
                            Didn't watch the vid, but in general the accuracy depends on the samples per sec. The default (60) is a low number pulled out of my backside, at least it has no measurable overhead.

                            But to get more accurate numbers, try "-t 1000" for example.

                            Now make a qt ui for it and I will award you 3845 brownie points. ;D
                            I don't really like Qt. Patches welcome

                            Comment


                            • #15
                              I have to two radeon graphic cards and one is blacklisted via xen pcihide. It seems that radeontop picks this graphic card. Everything is on 100%.

                              It would be nice to choose the graphic card.

                              Comment

                              Working...
                              X