3 ms·

I'd be a lot more interested in CPU usage, gnome is pretty terrible there and tend to either stutter, or worse - freeze for a while, quite often. It be interest

I'd be a lot more interested in CPU usage, gnome is pretty terrible there and tend to either stutter, or worse - freeze for a while, quite often. It be interesting to see if the alternatives are as bad.

pmontra 4y ago
Which GNOME are you using and on which hardware? I don't remember those problems with my old laptop from 2006 and with the one I'm currently using from 2014. Crashes happens, maybe not every year. I'm working with an Intel i7 4xxx, 32 GB RAM, SSD, GNOME shell 3.36, Ubuntu 20.04, NVIDIA Quadro K1100M. However I might have skipped some problems because I've been on GNOME Flashback for a while, from 2014 to 2020, while I waited for enough extensions to appear to recreated the saner (for me) environment before GNOME 3.
- vetinari 4y ago
  I have an older Ivy-bridge laptop from 2012 (Thinkpad T430s, 16 GB RAM, SSD) and it does indeed shutter occasionally in animations - I assume it tries to upload some asset for the GPU and it misses the presentation time. The overall performance is actually pretty nice for such old hardware.
- yxhuvud 4y ago
  I'm on wayland, using whichever version of gnome that come with ubuntu 22.10. Hardware is a 3950x with a radeon 5700xt. That should be more than plenty for being able to render firefox and a couple of electron apps (slack, discord) without stutter. Usually it works fine, but sometimes there is stutter or downright freezes. Note that it doesn't (currently) crash, the when a freeze happens it goes on for a while (30s?) and then go away.
  - pmontra 4y ago
    Your hw is beefier than mine. It could be Wayland (I'm on X11) but it shouldn't because it is designed not to stutter. It should definitely not freeze. Graphic card driver?
    - yxhuvud 4y ago
      Wayland as a protocol may be designed to be stutter-free, but the gnome compositor is very clearly not designed to be that. For example, it will happily request new frames or send new configuration events despite already being behind in processing what the client has produced so far. Which likely will make it fall even further behind, creating a bad circle.

pmontra 4y ago

Which GNOME are you using and on which hardware? I don't remember those problems with my old laptop from 2006 and with the one I'm currently using from 2014. Crashes happens, maybe not every year. I'm working with an Intel i7 4xxx, 32 GB RAM, SSD, GNOME shell 3.36, Ubuntu 20.04, NVIDIA Quadro K1100M. However I might have skipped some problems because I've been on GNOME Flashback for a while, from 2014 to 2020, while I waited for enough extensions to appear to recreated the saner (for me) environment before GNOME 3.

vetinari 4y ago
I have an older Ivy-bridge laptop from 2012 (Thinkpad T430s, 16 GB RAM, SSD) and it does indeed shutter occasionally in animations - I assume it tries to upload some asset for the GPU and it misses the presentation time. The overall performance is actually pretty nice for such old hardware.
yxhuvud 4y ago
I'm on wayland, using whichever version of gnome that come with ubuntu 22.10. Hardware is a 3950x with a radeon 5700xt. That should be more than plenty for being able to render firefox and a couple of electron apps (slack, discord) without stutter. Usually it works fine, but sometimes there is stutter or downright freezes. Note that it doesn't (currently) crash, the when a freeze happens it goes on for a while (30s?) and then go away.
- pmontra 4y ago
  Your hw is beefier than mine. It could be Wayland (I'm on X11) but it shouldn't because it is designed not to stutter. It should definitely not freeze. Graphic card driver?
  - yxhuvud 4y ago
    Wayland as a protocol may be designed to be stutter-free, but the gnome compositor is very clearly not designed to be that. For example, it will happily request new frames or send new configuration events despite already being behind in processing what the client has produced so far. Which likely will make it fall even further behind, creating a bad circle.