I’m experiencing same issue after upgrading to 390, even Youtube videos stutter noticeably for the first few seconds.
Best way for me to reproduce the issue is to run the WebGL 2.0 test (test 5/20) of Basemarks web benchmark:
[url]Basemark Web 3.0 | Main page
With 390 the loading (black screen) takes about 28 seconds. During that time the system is almost unusable (unresponsibe), even the hwcursor stutters…
With 387 is takes less than 1 second and everything’s smooth.
My system:
Distro: Gentoo
CPU: Ryzen 1800X
GPU: GeForce GTX 1080 Ti
Kernel: Linux 4.14.20
Browser: Chromium 64.0.3282.167 (full hardware acceleration according to chrome://gpu/)
GCC: 7.3.0
Just adding my own experience, the same issues happening with drivers 390. Reverting back to 384 (haven’t checked 387 but from comments should be safe) is solving the issue.
System:
i7 2700K @ 4500
8GB DDR3 1600MHz
GTX 970 4GB Mini
Gentoo Linux
Kernel 4.15.2
Browser: Chrome 65.0.3325.51, Vivaldi 1.14.1077.45_p1, Brave 0.20.41 (all of them had the issue)
i3wm
compton 0.1_beta2
Anyone else noticed GPU usage locked to at least 14% on this new driver (seen via nvidia-smi) when idle? It’s also causing a solid 2-4% CPU usage in top as “irq/37-nvidia”. Arch on kernel 4.15.5.
Something of note regarding the “stuck at 14% idle GPU usage” issue. It only seems to happen at 1920x1080 for me:
1080p
Mon Feb 26 14:01:20 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.25 Driver Version: 390.25 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 106... Off | 00000000:01:00.0 On | N/A |
| 0% 48C P8 7W / 120W | 49MiB / 6075MiB | 14% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 813 G /usr/lib/xorg-server/Xorg 26MiB |
+-----------------------------------------------------------------------------+
Then use xrandr to switch to 720p:
Mon Feb 26 14:06:28 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.25 Driver Version: 390.25 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 106... Off | 00000000:01:00.0 On | N/A |
| 0% 46C P8 5W / 120W | 22MiB / 6075MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 813 G /usr/lib/xorg-server/Xorg 20MiB |
+-----------------------------------------------------------------------------+
Switching back to 1080p causes the GPU usage to go back to 14%. This only happens on the 390.25 driver. I also get really bad black tearing across the screen at times (and almost constantly if I use VNC).
A theory: The CompositionPipeline flags are specific to metamode. Maybe the flags are only on for 1080p and the GPU is constantly compositing when those flags are enabled.
If you didn’t turn those flags on yourself, though, that’s unlikely.
Same issue for me running Arch + kwin + quad monitors + GTX 1070. Idle GPU usage was around 15%, Chrome was very laggy, and there were flashing black boxes on 3rd and 4th monitor when scrolling. Everything returned to normal when I reverted to 387.34 and kernel 4.14.15.
I’m on Manjaro at version 390.25 and everything runs just fine here.
The only issue I have is that I get massive performance losses, sometimes even dropping bellow 50% of what should be, if I upgrade my kernel to anything past 4.9
I’m using Linux 4.9 and steam games run really well. Past that, I get a huge performance impact.
Your setting is just applied once at startup when that mode gets set, but will be gone if you don’t mention it again when changing to a different mode.
There’s a second way to enable it through a line like this:
Option "ForceCompositionPipeline" "yes"
Using this instead of ‘MetaModes’, it will get applied to all modes you set.
Hi, I have a GTX 1050 from MSI and everything works perfectly (even games) less Chrome (and other Chromium browsers).
I have stuttering when I visit some concrete websites, like muycomputer.com, and the start page of the browser. These are the software and hardware I use:
GeForce GTX 1050 OC Edition from MSI as GPU (identified as GeForce GTX 1050/PCIe/SSE2 after installing the official driver)
ASUS ROG Strix X370-F GAMING as motherboard
AMD Ryzen 7 1700 eight-core as CPU
ASUS Xonar DSX as soundcard
Ubuntu 17.10.1 as operating system
GNOME Shell 3.26.2 vanilla as desktop environment, obtained from the package gnome-session (I have Ubuntu session too, but I don't use it)
I had similar problems using Fedora 27 Workstation and the NVIDIA official driver installed from RPMFusion. So I think it’s not a problem from implementation delivered from GPU Drivers, but a problem with the driver itself. Moreover, sometimes the stuttering affects the music too when I’m listening through Audacious (an audio player) and browsing with a Chromium Browser. For tests, I recommend to have a lot of tabs opened.
It seems that the 390 branch needs to improve yet.
I don’t know if this helps, but doing a little testing between kokoko3k’s image and my own, there is a consistent stutter triggered by I/O.
In games, when new graphical assets load (e.g. when an enemy with a model that hasn’t been loaded yet is about to be rendered) there is a noticeable stutter, system wide.
Here’s a quick and easily reproducible test: Play a video in VLC, then open Chromium. The video stutters as chromium loads. (I don’t think VLC matters here, but Chromium is a definite culprit. I used VDPAU output in VLC for both tests).
The stutter doesn’t happen on kokoko3k’s image. The video plays flawlessly. (or the stutter is < 1/24th second so not to interfere with the video)
I don’t believe it’s a disk I/O issue as I’m running everything from an nvme drive. Just to rule it out, here’s a quick benchmark:
hdparm -Tt /dev/nvme0n1
/dev/nvme0n1:
Timing cached reads: 25852 MB in 2.00 seconds = 12945.46 MB/sec
Timing buffered disk reads: 8022 MB in 3.00 seconds = 2673.95 MB/sec
Playing the video from a different disk and launching chromium, same issue.
This seems to be a similar issue as described by ColdLinux above.
I also do not have unusually high GPU utilization. Idle on the desktop it consistently 0-1%.