FS#57705 - [nvidia] bad performance with 390.25 drivers

Attached to Project: Arch Linux
Opened by DTA (demetulth) - Saturday, 03 March 2018, 01:57 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 21 March 2018, 20:48 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Felix Yan (felixonmars)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:
Experiencing major stuttering and performance issues in chromium with nvidia 390.25 drivers.
Many are rolling back to 387 because of the poor performance.

See thread here:
https://bbs.archlinux.org/viewtopic.php?id=234241
and
https://devtalk.nvidia.com/default/topic/1029484/-linux-mint-18-3-numerous-performance-amp-rendering-issues-on-390-25/?offset=27



Additional info:
* nvidia 390.25-14 drivers
* nvidia 1080 video card
* linux 4.15


Steps to reproduce:
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Wednesday, 21 March 2018, 20:48 GMT
Reason for closing:  Upstream
Comment by Peter (protake) - Wednesday, 14 March 2018, 16:12 GMT
This bug is still horrible. I'd greatly appreciate an update to the newest version as soon as possible.
Comment by loqs (loqs) - Wednesday, 14 March 2018, 18:44 GMT
@protake you are aware 390.42 does not fix the performance issues in chromium as acknowledged by nvidia https://devtalk.nvidia.com/default/topic/1029484/linux/-various-all-distros-numerous-performance-amp-rendering-issues-on-390-25/post/5245178/#5245178 or performance issues with other applications which nvidia has not responded to.
From the release notes the only fix it addresses is "Fixed a regression, introduced in 390.12, that caused occasional flicker when using the X driver's composition pipeline, for example when using screen transformations like rotation, or the "ForceCompositionPipeline" or "ForceFullCompositionPipeline" options."
Comment by Peter (protake) - Wednesday, 14 March 2018, 18:46 GMT
Oh, I was not aware. I thought the issue had been resolved. :/ Sorry then! It's really getting on my nerves.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 15 March 2018, 08:46 GMT
Honestly, I'm not sure what I can do here from a packaging perspective. I will close this issue soon in case no new hints turn up.

Loading...