5 ms·

The idea that the GNOME DE or GTK3/4 are resource intensive is a meme with little basis in reality.

Zababa 5y ago
This site asks for 1.5 Go of ram https://ubuntugnome.org/ https://ubuntugnome.org/, Ubuntu 20.04 asks for 4 Go of ram. Compared to the 30 Mo for IceWM in the article (apple to oranges, I know, but still 3 orders of magnitude), or the 300 Mo for KDE. The author also notes that since XFCE switched to GTK3 they use more resources. That seems to be plenty of basis in reality. Perhaps you mean something else by "resource intensive"?
- csande17 5y ago
  Keep in mind that the 1.5 GB number is the total amount of RAM you need to have a good time using the operating system, not the amount consumed by the window manager alone. Even OP consumes just about a gigabyte of RAM with all the programs on their Raspberry Pi. That's not to say GNOME _isn't_ resource intensive -- it is, especially when compared to desktop environments that were either written to be lightweight or written 30 years ago -- that just isn't the best way to measure it.
  - Zababa 5y ago
    > Keep in mind that the 1.5 GB number is the total amount of RAM you need to have a good time using the operating system, not the amount consumed by the window manager alone. That's why I said apples to oranges initially, but you're right, I could have clarified that part.
- alisonkisk 5y ago
  What's Go and Mo?
  - Narishma 5y ago
    Gigaoctet and Megaoctet. https://en.wikipedia.org/wiki/Octet_(computing) https://en.wikipedia.org/wiki/Octet_(computing)
  - jejones3141 5y ago
    o = "octet" (byte), so Go = gigabyte, Mo = megabyte.
pjmlp 5y ago
GTK3/4 alone not really, as my Linux netbook is doing just fine with XFCE. Now having GNOME with its Javascript based shell and extensions, making every click take a couple of seconds longer and me wondering what it is doing, no thanks.
- zxzax 5y ago
  The javascript is used mostly to drive the shell GUI, it shouldn't be taking seconds off all your mouse clicks. If there is really bad slowness, you should consider reporting that as a bug, it may not be the javascript that's at fault. The performance shouldn't be any worse than a typical lightweight web app running in firefox. That is of course if you ever end up using GNOME again for whatever reason. I don't understand why you have to wonder what it's doing, the javascript is all self-contained and hosted locally. It's not using npm or anything like that. And the extensions are pretty much the same as any other app you use that supports plugins.
  - pjmlp 5y ago
    "Memory leak in gnome-shell JavaScript bindings" https://access.redhat.com/solutions/3410651 https://access.redhat.com/solutions/3410651 "GNOME Shell Performance Improvements in Ubuntu 20.04" https://discourse.ubuntu.com/t/gnome-shell-performance-improvements-in-ubuntu-20-04/15972 https://discourse.ubuntu.com/t/gnome-shell-performance-impro... "Boosting the Real Time Performance of Gnome Shell 3.34 in Ubuntu 19.10" https://discourse.ubuntu.com/t/boosting-the-real-time-performance-of-gnome-shell-3-34-in-ubuntu-19-10/13095 https://discourse.ubuntu.com/t/boosting-the-real-time-perfor... When I complain about GNOME performance, I am not making it up, learn that and bye.
    - zxzax 5y ago
      I don't understand what the issue here is or what you want me to learn, those seem to all be bugs that were already fixed. If there are additional unfixed problems that others aren't aware of, and you're not making it up, then please mention those, and maybe I can help you get them reported.
badjeans 5y ago
https://www.google.com/search?q=gnome+3+memory+leak https://www.google.com/search?q=gnome+3+memory+leak https://www.google.com/search?q=gnome+3+cpu+use https://www.google.com/search?q=gnome+3+cpu+use sure...
- lobstrosity420 5y ago
  https://www.google.com/search?q=a+google+search+doesnt%27t+prove+anything https://www.google.com/search?q=a+google+search+doesnt%27t+p...

This site asks for 1.5 Go of ram https://ubuntugnome.org/ https://ubuntugnome.org/, Ubuntu 20.04 asks for 4 Go of ram. Compared to the 30 Mo for IceWM in the article (apple to oranges, I know, but still 3 orders of magnitude), or the 300 Mo for KDE. The author also notes that since XFCE switched to GTK3 they use more resources. That seems to be plenty of basis in reality. Perhaps you mean something else by "resource intensive"?

csande17 5y ago
Keep in mind that the 1.5 GB number is the total amount of RAM you need to have a good time using the operating system, not the amount consumed by the window manager alone. Even OP consumes just about a gigabyte of RAM with all the programs on their Raspberry Pi. That's not to say GNOME _isn't_ resource intensive -- it is, especially when compared to desktop environments that were either written to be lightweight or written 30 years ago -- that just isn't the best way to measure it.
- Zababa 5y ago
  > Keep in mind that the 1.5 GB number is the total amount of RAM you need to have a good time using the operating system, not the amount consumed by the window manager alone. That's why I said apples to oranges initially, but you're right, I could have clarified that part.
alisonkisk 5y ago
What's Go and Mo?
- Narishma 5y ago
  Gigaoctet and Megaoctet. https://en.wikipedia.org/wiki/Octet_(computing) https://en.wikipedia.org/wiki/Octet_(computing)
- jejones3141 5y ago
  o = "octet" (byte), so Go = gigabyte, Mo = megabyte.

pjmlp 5y ago

GTK3/4 alone not really, as my Linux netbook is doing just fine with XFCE. Now having GNOME with its Javascript based shell and extensions, making every click take a couple of seconds longer and me wondering what it is doing, no thanks.

zxzax 5y ago
The javascript is used mostly to drive the shell GUI, it shouldn't be taking seconds off all your mouse clicks. If there is really bad slowness, you should consider reporting that as a bug, it may not be the javascript that's at fault. The performance shouldn't be any worse than a typical lightweight web app running in firefox. That is of course if you ever end up using GNOME again for whatever reason. I don't understand why you have to wonder what it's doing, the javascript is all self-contained and hosted locally. It's not using npm or anything like that. And the extensions are pretty much the same as any other app you use that supports plugins.
- pjmlp 5y ago
  "Memory leak in gnome-shell JavaScript bindings" https://access.redhat.com/solutions/3410651 https://access.redhat.com/solutions/3410651 "GNOME Shell Performance Improvements in Ubuntu 20.04" https://discourse.ubuntu.com/t/gnome-shell-performance-improvements-in-ubuntu-20-04/15972 https://discourse.ubuntu.com/t/gnome-shell-performance-impro... "Boosting the Real Time Performance of Gnome Shell 3.34 in Ubuntu 19.10" https://discourse.ubuntu.com/t/boosting-the-real-time-performance-of-gnome-shell-3-34-in-ubuntu-19-10/13095 https://discourse.ubuntu.com/t/boosting-the-real-time-perfor... When I complain about GNOME performance, I am not making it up, learn that and bye.
  - zxzax 5y ago
    I don't understand what the issue here is or what you want me to learn, those seem to all be bugs that were already fixed. If there are additional unfixed problems that others aren't aware of, and you're not making it up, then please mention those, and maybe I can help you get them reported.

badjeans 5y ago

https://www.google.com/search?q=gnome+3+memory+leak https://www.google.com/search?q=gnome+3+memory+leak https://www.google.com/search?q=gnome+3+cpu+use https://www.google.com/search?q=gnome+3+cpu+use sure...

lobstrosity420 5y ago
https://www.google.com/search?q=a+google+search+doesnt%27t+prove+anything https://www.google.com/search?q=a+google+search+doesnt%27t+p...