Page 6 of 6 FirstFirst ... 456
Results 51 to 58 of 58

Thread: Announcing radeontop, a tool for viewing the GPU usage

  1. #51

    Default

    Thank you Its very enlightening - 15-25% usage on a 1080p h.264 encode, minetest takes 30-40%, FreeDoom 20-30%, idle desktop with 2* 1920x1200 0-3%, with a Radeon 4870 graphics card - i.e. nowhere near using the card, yet in minetest's case things are considered 'GPU limited'.

    Just yesterday I got kernel v3.9 with Debian Testing, I guess when Mesa goes to v9.2 I can finally move from Open GL 2.1 -> 3.1 or 3.3. Will be very interesting to see if minetest fps goes up, I can finally use the best VPU plugin with pcsx2, and what radeontop says about all this.

  2. #52

    Default

    Finally got round to making a script to output the GPU info somewhere useful then conky can read it in (intended to be ran as root, via an init.d script):

    Code:
    #!/bin/bash
    
    
    # Make sure the directory structure is in place
    [[ ! -d '/run/shm/radeontop' ]] && mkdir -p '/run/shm/radeontop'
    
    # Removing old data
    rm '/run/shm/radeontop/gpu' 2>/dev/null
    
    while true
    do
        # Running radeontop in dump mode, killing off the silly full buffering and outputting just the GPU stats. AWK's redirection fails - you must close the file to have it behave like a bash overwrite, and if you don't close or don't insert an arbitrary delay prior to the print (e.g. system sleep/beep call), nothing is output!
        stdbuf -oL radeontop -d - | awk '($2 == "gpu") { print substr($3, 1, length($3) - 1) > "/run/shm/radeontop/gpu"; close("/run/shm/radeontop/gpu"); }'
    done
    Had great difficulty getting AWK to do its job - looks like some strange buffering is happening if you don't close the file and don't arbitrarily delay the command.

  3. #53
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,729

    Default

    Apparently it's been ported to OpenBSD with no code changes. Nice to know, I wasn't expecting that.

    Now, anyone running the AMD blob (on Linux) willing to try it? I wonder if it also works with the blob. If so, the case for PTS integration would be clear - "is it cpu or gpu limited" result for every AMD graphics test

  4. #54
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,729

    Default

    Rejoice, for a new release is available! From Russia with love.

    v0.7
    This release comes with many locale fixes and a complete Russian
    translation.

    The pci ids were updated to detect Oland, Hainan, Bonaire, Kabini, and
    Kaveri. Dumping works better in pipes.

  5. #55

    Default

    Are there any plans to report on the VRAM usage? I've just discovered the gallium_hud functionality in mesa, and appreciated the VRAM graph there.

  6. #56
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,729

    Default

    I don't think that information is available via a register. Only the memory manager knows how much is used, and it currently only exports that information in debugfs.

  7. #57

    Default

    Cheers - I'll look into that.

  8. #58
    Join Date
    Mar 2013
    Location
    Kanpur
    Posts
    2

    Default

    wow!! great reply. really interesting. Cheers!!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •