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

Significant performance reduction after R3.2 -> R4.0 upgrade #3803

Closed
kravietz opened this Issue Apr 8, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@kravietz

kravietz commented Apr 8, 2018

Qubes OS version:

R4.0

Affected component(s):

All applications, most notably Chrome, Firefox


Steps to reproduce the behavior:

After R3.2 -> R4.0 upgrade the performance of all GUI apps was significantly reduced. This is most visible with Chrome and Firefox, but applies to any GUI application.

Expected behavior:

In R3.2 applications were responding immediately with no visible delay. I installed R4.0 over fully upgraded R3.2 just a few days ago. Unfortunately I'm unable to provide benchmarks for R3.2 as it's my primary working computer and downgrade is not feasible.

Actual behavior:

Responsiveness of the applications dropped dramatically to a point where you actually wait for a fraction of second for application to respond to a mouse click etc. Video playback is practically impossible, they are being displayed frame-by-frame, like a slow GIF animation.

General notes:

Kernel messages attached

dmesg.txt


Related issues:

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Apr 8, 2018

Member

Duplicate of #3639

Member

andrewdavidwong commented Apr 8, 2018

Duplicate of #3639

@andrewdavidwong andrewdavidwong marked this as a duplicate of #3639 Apr 8, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Apr 8, 2018

Member

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Member

andrewdavidwong commented Apr 8, 2018

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment