maemo.org - Talk
Page 6 of 7 « First 45 6 7
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)
-   -   [SFOS][1.1.0.27][OOM] The death of multitasking? (https://talk.maemo.org/showthread.php?t=94358)

m4r0v3r 2014-12-27 00:51
Re: [SFOS][1.1.0.27][OOM] The death of multitasking?
 
they can put this stuff in the utilities section in the settings

salyavin 2014-12-27 01:34
Re: [SFOS][1.1.0.27][OOM] The death of multitasking?
 
Yea I think that's a good place for it.

messing with settings described in this thread seems to have totally fixed it for me. Have gpodder, tweetian, tt-rss, android weechat, meecast, and I can launch the browser from tt-rss to read a full article and I have no issues at all, nothing is killed.

willi6868 2014-12-27 11:59
Re: [SFOS][1.1.0.27][OOM] The death of multitasking?
 
Quote:
Originally Posted by synt (Post 1453998)
The only tweak I've made is to increase vm.swappiness to 60 in /etc/sysctl.d/vm.conf file.
I also tweaked this value now and it seems to work quite well till now.

BTW if someone doesn't follow the TJC thread - a Jolla employee just posted an comment:

Quote:
Originally Posted by tigeli
Ok, in short... you can play with these:
  • /sys/module/lowmemorykiller/parameters/adj (0,58,117,529,1000)
  • /sys/module/lowmemorykiller/parameters/minfree (4096,6144,8192,12288,20000)
  • /proc/sys/vm/extra_free_kbytes (16384)

First sets oom_score-values for group of apps running inside of those values, second sets the values how much memory should be always available before killing apps in that group starts. Third sets the value of how much memory should always kept free.

Example.. apps having oom_score between 0 and 57 will not be killed before the memory has gone below 40964 = 16384kB. Apps having oom_score 1000 will be killed if there is less than 200004 = 80000kB available memory.
Maybe someone could provide some nice values for fine tuning. :)

nthn 2014-12-27 12:55
Re: [SFOS][1.1.0.27][OOM] The death of multitasking?
 
If you want something added to the Utilities to change OOM stuff: https://github.com/sailfishos/sailfish-utilities

catbus 2014-12-27 14:24
Re: [SFOS][1.1.0.27][OOM] The death of multitasking?
 
^nothing _new_ ...

salyavin 2014-12-29 02:11
Re: [SFOS][1.1.0.27][OOM] The death of multitasking?
 
Had one app close today and gave up and did
"echo "0,0,0,0,0" > /sys/module/lowmemorykiller/parameters/minfree"
from https://together.jolla.com/question/...#comment-73891

w00t 2014-12-29 02:58
Re: [SFOS][1.1.0.27][OOM] The death of multitasking?
 
Quote:
Originally Posted by ste-phan (Post 1453928)
So there seems to be a major change with regard to Android programs. I thought previously, Android Myriad Dalvik just had 512MB RAM at max and the rest would remain reserved for Jolla?
There's been a lot of changes. One of them is that Android is now subject to the same behaviour as the rest of the device, whereas previously, Android was allowed to kill off everything else and swap the device into oblivion (or reboot), which serves to make the behavior a bit more visible for people who use a lot of Android applications.

w00t 2014-12-29 03:09
Re: [SFOS][1.1.0.27][OOM] The death of multitasking?
 
Quote:
Originally Posted by m4r0v3r (Post 1453995)
I used to have issues with lag at times, but nothing to serious the device would stop functioning.
The problem is that everyone is not you. Different people use their devices in different ways, run different software, emphasize different features.

One favorite bug as an example for this that I helped fix a few months ago was a SQL query in Messages taking well over a second for someone (freezing the UI the whole time), whereas for me it didn't even take more than 20ms. Something on his device was clearly off. I never really looked into that part, rather hard to do remotely, but I did fix the query: https://github.com/nemomobile/libcom...a02b61a74a3192

szopin 2015-07-14 01:50
Re: [SFOS][1.1.0.27][OOM] The death of multitasking?
 
Quote:
Originally Posted by salyavin (Post 1454229)
Had one app close today and gave up and did
"echo "0,0,0,0,0" > /sys/module/lowmemorykiller/parameters/minfree"
from https://together.jolla.com/question/...#comment-73891
Has anyone figured out how to properly kill/disable lowmemorykiller? Neither tweaking overcommit_ratio, nor this minfree trick stops the lowmemorykiller from killing cc1plus when compiling on device.

Ok, from my testing this seems to kill oom-killer for good:
Code:
echo '9999' > /sys/module/lowmemorykiller/parameters/adj
echo '1' > /sys/module/lowmemorykiller/parameters/minfree
your process will die if it eats all swap+ram, but other apps stay alive
thanks to nieldk

dameceno 2017-03-20 11:31
Re: [SFOS][1.1.0.27][OOM] The death of multitasking?
 
Quote:
Originally Posted by szopin (Post 1476562)
Has anyone figured out how to properly kill/disable lowmemorykiller? Neither tweaking overcommit_ratio, nor this minfree trick stops the lowmemorykiller from killing cc1plus when compiling on device.

Ok, from my testing this seems to kill oom-killer for good:
Code:
echo '9999' > /sys/module/lowmemorykiller/parameters/adj
echo '1' > /sys/module/lowmemorykiller/parameters/minfree
your process will die if it eats all swap+ram, but other apps stay alive
thanks to nieldk
This commands might have worked previously but on 2.0.5.6 I still get apps being killed and some lagging behavior at times.
What are the commands to revert this please?


All times are GMT. The time now is 17:51.
Page 6 of 7 « First 45 6 7
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8