You are not logged in.
Hi,
Ive been noticing nvidia usage to be unusually high, around 23% when the system is idle but 'only' if the screen orientation is changed to portrait.
So in other words, if the sreen is in portrait and the system is idle usage is around 23%, but if the system is busy with lets say browsing the web the usage drops to around 11%
and then when its idle again, usage spikes back to 23%
Once I change the orientation back to landscape the gpu usage normalizes. Since I have a desktop I dont use intel graphics and use nvidia for X.
I used xrandr:
xrandr --output DP-1 --rotate right
to change the screen orientation picking right from the available options at:
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 509mm x 286mm
1920x1080 60.00*+
1680x1050 59.95
1600x900 60.00
1440x900 59.89
1280x1024 60.02
1280x800 59.81
1280x720 60.00
1024x768 60.00
800x600 60.32
640x480 59.94
Do I have to change some other settings as well? Let me know if you need to view any logs, so far I havnt seen any errors, at least not that I know of..
Any tips / suggestions?
Thanks!
Last edited by Kabir (2018-11-08 22:00:58)
Offline
The rotation requires the full composition pipeline. Is the behavior similar when you just enforce it?
Also the desktop session, WM, compositor might be relevant.
Offline
Yes, unfortunately theres no change in behavior after enforcing full composition pipeline, in fact, with full composition pipeline enabled
I get the same results even in landscape mode. Killing compton and repeating the above steps doesnt change anything.
So its got to be either the desktop session or WM (i3), right?
Offline
That's pretty much what I expected, so it's related to the composition pipeline.
Try passing
Option "UseNvKmsCompositionPipeline" "false"
to the driver (via an xorg configlet)
Offline
That fixed it, thanks so much!
Offline
Beware that this is probably a transitional config and that the kms composition pipeline might become inevitable. So if it doesn't magically fix itself, you may want to file a bug w/ nvidia.
https://devtalk.nvidia.com/default/topi … his-first/
https://devtalk.nvidia.com/default/topi … -on-linux/
Offline
Oh ok. Well thanks for letting me know, I'll file a bug if that happens.
Offline