Originally posted by RealNC
View Post
Announcement
Collapse
No announcement yet.
An Important GNOME Performance Fix Has Landed
Collapse
X
-
-
Originally posted by franglais125 View Post
This only impacts Wayland!
I ask because the bug report is testing with glxgears, which runs through x11 - not testing with a native Wayland application, and the final comment of the bug report mentions that the bug can be anywhere in the "glx => xwayland => Mutter => KMS" path
Leave a comment:
-
Not sure what exactly 12.97 ms refers to. Is that once a second? When I run Gnome on Ubuntu 17.10, X11, SystemMonitor shows all CPUs ~5% or lower, about 20% total. When I move the mouse over highlighting stuff, one of the curves will go up to about 40% for a moment.
Is their anything around 75% (12.97 / 16.66) with 18.04 and Wayland?
Leave a comment:
-
The "improved" 12.97ms number really sounds very disappointing.
I could run Gnome on Ubuntu 8.04 very smoothly on a 300 MHz Pentium 3, which is probably 100x slower than my current PC.
And with the current "new tech" stack on 100x faster hardware, rendering the idle desktop takes 13 ms of the 16 ms available for a frame? If true, this feels like we're moving backwards.
- Likes 2
Leave a comment:
-
Originally posted by Holograph View PostWait, what? This assumption would only hold true with fixed-width fonts. You can't use (just) the length of a string to determine how to do layout with a variable width font. The whole idea behind this commit sounds broken and I'm not sure why that wouldn't be obvious. Am I missing something here?
Leave a comment:
-
Originally posted by Brisse View Post
Were you running Wayland? I run my monitor at 120hz and GNOME on Wayland is absolute stutterfest, but it runs fine on x.org.
There are things that affect Gnome-Shell performance since forever..., back in the day we could solve it wih "CLUTTER_PAINT=disable-clipped-redraws:disable-culling" and that was the only method that made GS usable and quite smooth to be honest, unfortunately, back in 3.18 (or maybe 3.20 not sure) that got broken and bug report for it stays opened..., so pretty much only method that made GS usable got broken and forgoten about.
Unfortunately also, even with those performance issues and generally terrible lags that got worse by every release, I can't see myself using any other DE, and no, don't even mention KDE to me, if it works for you, brilliant, good for you, I do not like it at all, so even if it worked better i still wouldn't use it, and that's about it.
Leave a comment:
-
Originally posted by Holograph View PostWait, what? This assumption would only hold true with fixed-width fonts. You can't use (just) the length of a string to determine how to do layout with a variable width font. The whole idea behind this commit sounds broken and I'm not sure why that wouldn't be obvious. Am I missing something here?
Leave a comment:
-
Wait, what? This assumption would only hold true with fixed-width fonts. You can't use (just) the length of a string to determine how to do layout with a variable width font. The whole idea behind this commit sounds broken and I'm not sure why that wouldn't be obvious. Am I missing something here?
Leave a comment:
-
Originally posted by Vash63 View Post
Interesting. I'll definitely be sticking with Xorg for a bit given all the problems on Wayland. Reading this bug report it looks like this only impacts X11 applications?
Leave a comment:
-
Originally posted by franglais125 View Post(cc RealNC ) This might be becase Gnome on Wayland is fixed at 60Hz, whatever your monitor refresh rate is. https://bugzilla.gnome.org/show_bug.cgi?id=781296
Leave a comment:
Leave a comment: