3 ms·

Interesting, MATE should be under 400MB or less if you do not enable optional HUD or tray resident applications. Even in 64bit, it ran just fine on a pi2b wit

Interesting, MATE should be under 400MB or less if you do not enable optional HUD or tray resident applications. Even in 64bit, it ran just fine on a pi2b with 512MB ram, and was about 340MB at boot-up with marco (no colord, HUD terminal, or evolution mail etc.). The issue arises in how linux reuses ram pages for shared objects. While you may have many processes... the actual incremental program size can be very small. One of the many reasons oversized kernel ram cache/buffer sizes can help with performance (often as high as 40% on small flash memory io-constrained devices). A heavily customized MATE on Ubuntu LTS OS is part of the standard developer platform I recommend. This takes a bit of effort, but there are benefits to having everyone on the exact same hardware, OS, and compiler version. i.e. cloning/repairing a workstation snapshot takes 30 minutes.

itvision 4y ago
Fedora results are somewhat bloated given the presence of packagekitd but since all the spins run it, you can still make valid conclusions.
- Joel_Mckay 4y ago
  Fedora and its community derivatives can be problematic for developers... as the security-policies, application and driver-support can sidetrack projects. Better for DNS/db/key servers, if you aren't allowed to use *BSD because "reasons". Sometimes a hardened system is not ideal when you are trying to debug something complicated already. Something like alpine-linux is also intended for specific uses-cases.
mk_stjames 4y ago
I have Ubuntu 20.04 running MATE on a RPi 4 8GB and I have to say it is pretty damn sluggish. I need to dig under the hood more to lighten it up, because even with a quad core at 1.5ghz and 8gb ram... the window system and just general menus and movement feels slower than an old Win2K machine I had with only 64MB of ram at 266mhz. I had to enable the outline-of-window-only when moving or resizing because just moving a firefox window on the screen drops the FPS to a slideshow.
- Joel_Mckay 4y ago
  The out-of-the-box performance on the pi4 is a drag, OpenGL support has been silently crippled in many repo applications for compatibility reasons, and overclocking the sdcard is more limited than the pi2/pi3 (primary bottleneck). You may have to brute force the marco GPU flags to figure out which features are implemented, don't break video codecs, and don't conflict with kernel settings (v4l driver). There are a dozen reasons things may be glitched, but usually it is the lack of active cooling causing the pi4 to thermal throttle. Also, mate-tweak tool can save time digging for settings. Also, if it is the Ubuntu distro rather than Raspbian, than there is a lot of missing software to get things working well. Best of luck =)

itvision 4y ago

Fedora results are somewhat bloated given the presence of packagekitd but since all the spins run it, you can still make valid conclusions.

Joel_Mckay 4y ago
Fedora and its community derivatives can be problematic for developers... as the security-policies, application and driver-support can sidetrack projects. Better for DNS/db/key servers, if you aren't allowed to use *BSD because "reasons". Sometimes a hardened system is not ideal when you are trying to debug something complicated already. Something like alpine-linux is also intended for specific uses-cases.

mk_stjames 4y ago

I have Ubuntu 20.04 running MATE on a RPi 4 8GB and I have to say it is pretty damn sluggish. I need to dig under the hood more to lighten it up, because even with a quad core at 1.5ghz and 8gb ram... the window system and just general menus and movement feels slower than an old Win2K machine I had with only 64MB of ram at 266mhz. I had to enable the outline-of-window-only when moving or resizing because just moving a firefox window on the screen drops the FPS to a slideshow.

Joel_Mckay 4y ago
The out-of-the-box performance on the pi4 is a drag, OpenGL support has been silently crippled in many repo applications for compatibility reasons, and overclocking the sdcard is more limited than the pi2/pi3 (primary bottleneck). You may have to brute force the marco GPU flags to figure out which features are implemented, don't break video codecs, and don't conflict with kernel settings (v4l driver). There are a dozen reasons things may be glitched, but usually it is the lack of active cooling causing the pi4 to thermal throttle. Also, mate-tweak tool can save time digging for settings. Also, if it is the Ubuntu distro rather than Raspbian, than there is a lot of missing software to get things working well. Best of luck =)