Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RCS usage view percentage change is slow and breaks when changing "OA visible sampling" #178

Open
eero-t opened this issue Apr 27, 2018 · 2 comments

Comments

@eero-t
Copy link

eero-t commented Apr 27, 2018

I was running everything on the same machine (gputop server & ui and test-case), with up to date Ubuntu 16.04 and latest Mesa git version.

Test-case:

  1. start gputop-ui
  2. "Multi contexts" -> "RCS usage"
  3. Start GpuTest v0.7 FurMark in windowed mode (I think any heavy 3D test would do)
  4. Wait until "RCS usage" has stabilized
  5. Drag with mouse the "OS visible sampling" slider from 7s to 2s

At step 3), GpuTop takes all GPU idle time, and other RCS percentages decrease as GPU ramps to full speed. The change in the shown percentages takes many seconds, although in reality the change happens instantly. I assume this view uses some kind of running overage, over the whole 7s. While this "animates" the transitions, it will hide faster changes. IMHO averaging should by default be over smaller period.

To see transitions easier, I changed sampling to 2s in step 5). After the animation, "RCS usage" showed 70% idle, although GPU is still 100% busy. This is obviously a bug.

@djdeath
Copy link
Collaborator

djdeath commented Apr 27, 2018

The RCS usage is computed based on the visible part of the timeline.
If you zoom on part of the timeline, the usage will be computed just for that zoom and by default it covers the 7s timeline.
It's not really obvious, although the usage window displays the amount of time used to compute the percentages.

@eero-t
Copy link
Author

eero-t commented Apr 27, 2018

Although the "animation" / slowness looks a bit odd, I don't care about it that much. But it showing GPU as being mostly idle when GPU remains 100% busy (also according to OA counter), is a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants