It's known that driver support is bad. But I think the main problem with gnome is that it uses js. Its runs a whole damn browser (firefox). It's js that owes to the numerous memory leaks that end up hogging extreme amounts of memory.
It's known that driver support is bad. But I think the main problem with gnome is that it uses js. Its runs a whole damn browser (firefox). It's js that owes to the numerous memory leaks that end up hogging extreme amounts of memory.
Also, I don't think it's unlikely you found different desktops that perform better. I still find KDE on proprietary NVIDIA to be lackluster. Does it show it's possible to do better compositing on some setups? Yes. I am guessing GNOME relies on the existence of certain GL extensions to composite efficiently. Still: if it can perform well on super low end systems and poorly on high end ones, I doubt it has to do with JS.
Even if you ignore the memory leak (and say that it's being fixed) I would argue that the overall latency of the desktop is just not there. I have used xfce, gnome3, unity7, kde, mate and budgie (daily driver) on the same machine, with the same Intel iGPU Mesa driver; gnome3 is the most sluggish. The time it takes for stuff to happen on the screen from when I press a button is quite high for my taste.
P.S. I usually disable animations.
The design of the desktop is definitely unique and admittedly refreshing to see (except the hamburger menus). However, the sluggishness just makes it impossible for me to use.
https://gitlab.gnome.org/GNOME/gnome-shell/graphs/master/cha...
Exactly why budgie desktop is fast. Uses Mutter as WM, and the gnome applications (like Nautilus, control centre).
For instance, gnome-shell starts up at around 150MB of memory usage, climbs upto around 1GB, eventually halting.
OTOH, budgie-wm stays at a cool 25-30 MB usage.
More on how the budgie thing works : https://budgie-desktop.org/2017/01/25/kicking-off-budgie-11/