Krišjānis Nesenbergs

less info
181 reputation
16
bio website
location
age
visits member for 2 years, 11 months
seen May 3 '13 at 13:50

May
27
awarded  Self-Learner
Feb
23
awarded  Notable Question
Apr
12
awarded  Popular Question
May
25
awarded  Teacher
May
25
awarded  Scholar
May
25
accepted Computer freezing on almost full RAM, possibly disk cache problem
May
25
revised Computer freezing on almost full RAM, possibly disk cache problem
Updated more precise information, rewrote some unrelevant paragraphs; added 154 characters in body
May
24
answered Computer freezing on almost full RAM, possibly disk cache problem
May
21
revised Computer freezing on almost full RAM, possibly disk cache problem
added 57 characters in body
May
21
awarded  Editor
May
21
revised Computer freezing on almost full RAM, possibly disk cache problem
added 1008 characters in body
May
10
comment Computer freezing on almost full RAM, possibly disk cache problem
Anyway - swapping and the amount of RAM is a bit offtopic. Te problem is, that system becomes unresponsive for a long time, even if swap is disabled, and after that sometimes still runs the program (so it manages to find memory somewhere) and other times runs oom_killer. The system should be able to tell it is running out of ram and just not let me run more stuff. So is there any way to stop those freezes or set the priority of user input so high, that I can switch to console when they happen and kill some processes myself?
May
10
comment Computer freezing on almost full RAM, possibly disk cache problem
I have 2GB Ram and the HDD is 5400rpm. I really dont think that it is such an old system which justifies half an hour freezes while watching some video on one monitor and browsing some 20-30 tabs in the other. Actually I would be quite happy if I just could allways access console and kill some processes - is there a way to make user input and terminal super high priority so it works while system freezes?
May
10
comment Computer freezing on almost full RAM, possibly disk cache problem
The problem is, that oom_kill just doesn't get called before the computer has locked up for some 30 minues. Also - is there at least a way to know which process will be killed first?
May
10
comment Computer freezing on almost full RAM, possibly disk cache problem
Actually reducing swapiness reduced the problem (it happened more rarely). I am keeping it at 5 now. Although maybe it was another problem with higer swapinness, because, when it was 60, and I decided to watch a movie or edit a big file, whole file og almost a GB was loaded in memory and then instantly system started swapping out programs I was actively using and even user interface itself. The thing is I think I understand the swapping part, what I want is killing greedy user applications instead of freezing the machine when running out of ram. (And preferably limit file size in cache)
May
10
awarded  Student
May
10
asked Computer freezing on almost full RAM, possibly disk cache problem