Originally posted by debiangamer
View Post
Announcement
Collapse
No announcement yet.
Yes, Linux Does Bad In Low RAM / Memory Pressure Situations On The Desktop
Collapse
X
-
Originally posted by loganj View Postwell windows if is running out of ram will start to close applications. of course you'll be asked to close some applications but if you don't respond than windows will make a choice for you.
but if you have swap on (i forgot the name of it) than you'll be safe but still will have a lot of hdd writes
Comment
-
Originally posted by skeevy420 View Post
I consider it user error and not a deficiency of the OS. The user pushing something too hard isn't necessarily a computer problem for that matter. No matter how many safe guards are in place, it doesn't help it if a user pushes something beyond its limits. In this case they removed a safe guard and pushed it beyond its limit.
How is the kernel supposed to know if it needs to halt Plasma, Firefox, Mplayer, LibreOffice, KSP, Kate, Yakuake, makepkg or what to keep the system in a usable manner? All it can do is juggle stuff with what little resources it has available.
IMHO, this is really a problem that should be solved by a daemon that a user can configure it to kill/halt/suspend-to-disk programs in a specific order because the kernel can't read my mind to know what I consider to be the more important task. It would also need a blacklist of things to not kill ever like the actual desktop environment.
- Likes 2
Comment
-
This doesn't make any sense. If you run out of memory and don't have a swap file I'm surprised the system runs at all. I sincerely don't understand the complaint.
For goodness sake, just create a swap file and you'll be fine. Of course it won't run as fast as it would with more memory, but I know from many years of experience with low memory systems in the old days that the performance is more than acceptable.
- Likes 1
Comment
-
- Likes 3
Comment
-
Originally posted by timofonic View PostWhat about automatic recovery?
I think it would be good to also have some application-specific mechanism though: The critical data in a LibreOffice instance are large, but compress exceedingly well; but there's also lots of crap in that process's memory that doesn't really need to be saved. LibreOffice already has a lot of recovery code, what's a bit more?
- Likes 1
Comment
-
Originally posted by gamerk2 View PostThe behavior being described here sounds like a bug that is being exposed in a low RAM condition; if both main memory and the swap file is full/disabled, why is the OS locking up performing I/O to the HDD? That sounds like a separate problem then what most people are talking about here right now. I think the obvious thing to check is what the OS is attempting to do in this condition, because it doesn't sound correct to me.
if swap is been used, you will have IO on the disk( there are other processes running, and swap out/in takes IO to the roof )..
Comment
-
Originally posted by muncrief View PostThis doesn't make any sense. If you run out of memory and don't have a swap file I'm surprised the system runs at all. I sincerely don't understand the complaint.
For goodness sake, just create a swap file and you'll be fine. Of course it won't run as fast as it would with more memory, but I know from many years of experience with low memory systems in the old days that the performance is more than acceptable.
- Likes 1
Comment
Comment