Originally posted by milkylainen
View Post
Announcement
Collapse
No announcement yet.
Yes, Linux Does Bad In Low RAM / Memory Pressure Situations On The Desktop
Collapse
X
-
- Likes 1
-
Originally posted by slavko321 View Post
If you run out of RAM, the OOM killer should be called immediately. Right now there is a long period of disk trashing even if you have NO swap enabled.
This is obviously a bug.
And alt-sysrq-f is a lifesaver
Evidence. Millions of Android devices, laptops with ChromeOS are fully functional (with Linux kernel). The manufacturer and supplier of the operating system care about this. GNU/Linux distributions no.
The administrator (you) must correctly configure the system according to your needs.
- Likes 2
Comment
-
Open a few tabs in a web browser and you crash 4GB of RAM? What kind of crap system does that? I've been using GNU/Linux distros over 20 years, and never seen that behavior. Never been a Ubuntu user - is this a Ubuntu problem? Not a problem on a sane distro like opensuse or Debian.
Maybe it's a Chrome problem - Chrome on Windows is a memory disaster if I recall correctly. Even after closed it used to keep running 5-6 orphaned processes that would hog as much available memory as possible. Friends should not let friends use Chrome.
- Likes 4
Comment
-
Originally posted by kpedersen View PostIn the RHEL4 / Fedora Core 4 days, it was quite common for a laptop to only have 512M of RAM; Fedora Core 4 ran terribly. Then Fedora Core 5's installer didn't even work on 512M, just uncompressing the package data caused it to run out and abort.
- Likes 1
Comment
-
Originally posted by latalante View Post
In my opinion, this is not a bug.
Evidence. Millions of Android devices, laptops with ChromeOS are fully functional (with Linux kernel). The manufacturer and supplier of the operating system care about this. GNU/Linux distributions no.
The administrator (you) must correctly configure the system according to your needs.
Chrome/ChromiumOS also uses additional tooling to avoid dealing with the mainline OOM detection.
- Likes 12
Comment
-
Pages get evicted fairly randomly under pressure, so you have things that are actually used sent out to the swap partition only to be brought back and this could happen multiple times. The LRU doesn't have the information needed to intelligently make decisions about this.
- Likes 1
Comment
-
Originally posted by dimko View Post
Because your machine can not possibly have issues of it's own. Also, swap is not substitute for proper hardware.
As an example, Linux makes an HDD look fast, while Windows needs an SSD to be fast.
Also, please note that this was in 2015 when I only had 8GB RAM in my system. I then upgraded to 16.
(This still occurs with my dad's 1GB laptop, however, and we'd love to fix it but sometimes we have fights and not enough money which distances us from the solution)
- Likes 11
Comment
-
Originally posted by Space Heater View Post
Android has used a non-mainline LMK (low memory killer) and is now using PSI monitoring for OOM killer heuristics.
Chrome/ChromiumOS also uses additional tooling to avoid dealing with the mainline OOM detection.
- Likes 1
Comment
-
IMO linux should do something like that: Have something like zram with a high performance / lower compression algo (lz4?) stand by... when memory starts approaching critical levels, start compressing the ram incrementally to prevent the "huge stall".
In terms of dealing with memory offenders, perhaps there should be something like a service that monitors apps that eat up memory aggressively. When it predicts that they will be OOM in the next few miliseconds, kill the offending app.
- Likes 1
Comment
Comment