I absolutely love how much more responsive GNOME has gotten in recent releases. GNOME 3 used to be so ridiculously slow and painful to use.
Announcement
Collapse
No announcement yet.
GNOME 40 Mutter Moves Input Work To A Separate Thread
Collapse
X
-
Originally posted by sabian2008 View PostIs this only for Wayland?
Finally. It was probably one of the biggest (if not biggest) flaw in GNOME Wayland session. It was very annoying seeing cursor lags with heavy IO. I hope it will be finally gone with these patches.Last edited by dragon321; 28 November 2020, 11:18 AM.
- Likes 9
Comment
-
Originally posted by S.Pam View PostI was using multi-threaded applications on the Amiga days... What happened - why isn't important and critical things not in separate worker threads already?
Gnome started 1997 Intel Pentium II time frame this is a single core cpu right. Go back with X11/x.org server it also starts on single core cpus. Horrible as it sounds on a single core cpu the best performance is not separate worker threads but single threaded. So at the start of both of these projects it not broken to go single thread and separate workers on the systems they started on was going to use more cpu time so perform worse back then.
Then everything slowly but surely builds on top of this framework. Now you have something in your project like the Giant lock https://en.wikipedia.org/wiki/Giant_lock what Linux world would big kernel lock. Where different code all of the place depends on the fact that what is in the single threaded is basically locked against itself and will only happen in that exact order. Remember linux kernel had to write a tool lockdep https://www.kernel.org/doc/Documenta...dep-design.txt to dig themselves out of stack of single thread code at its core. Yes early Linux kernel also started on single core cpus so single threaded core parts was right.
This is one of these problems where the choice at the start is right but over time it comes wrong and the nightmare is that its not a little wrong you have dug yourself into a complex hole where you have implement locking as well as working out what parts can truly be run without locking against each other. Lots of fun cases of dead locks for anyone attempting to fix this problem to over come as well.
Notice Linux kernel had to make lockdep. Did gnome need to make a tool as well kind of it was adding support to sysprof to handle the core shell of gnome(kind allows you to see where a deadlock is).
Basically easy to create very hard to dig you way out of. All giant lock problems are multi year fixes and are like to be ignored by developers as they go and do other easier work Gnome is not a special case here.
- Likes 3
Comment
-
Originally posted by ix900 View PostOkay, we now know your love for Amiga lol. Sadly, it wasn't impressive enough to have gone anywhere. You can cuddle it in a blanket and rock it to sleep if you want.
Comment
-
Originally posted by 144Hz View PostJackLilhammers Why PopOS?- When I try out something on Linux I usually do on Ubuntu based distributions
- PopOS is more user friendly for Nvidia and Optimus laptops
- I'm not a huge fan of Fedora
- There are lots of other options available, but IMHO for testing just Gnome is not worth exploring alternatives
Comment
-
Originally posted by dragon321 View PostOn X11 it's X Server job to handle input and window manager/compositor is separate process.
http://software.cfht.hawaii.edu/man/x11/XInitThreads(3x)
Horrible reality if you don't call XinitThreads x.org server from your windows manager and compositor(if you have one) x.org gets to go back to being pure single threaded supply of stuff to the windows manager and compositor.
Originally posted by dragon321 View PostOn Wayland compositor does everything that X Server does so it needs to handle input as well. Obviously such patches are not needed for X.Org session..
Originally posted by dragon321 View PostFinally. It was probably one of the biggest (if not biggest) flaw in GNOME Wayland session. It was very annoying seeing cursor lags with heavy IO. I hope it will be finally gone with these patches.
- Likes 8
Comment
Comment