Active Topics
-
Firefox with Leste (5)
to Maemo 7 / Leste by teroyk - 3 days, 4 hrs ago -
Handbook (2)
to Maemo 7 / Leste by teroyk - 4 days, 4 hrs ago - more...
m4r0v3r |
2014-12-27
, 00:51
|
|
Posts: 1,746 |
Thanked: 1,832 times |
Joined on Dec 2010
|
#51
|
they can put this stuff in the utilities section in the settings
| The Following User Says Thank You to m4r0v3r For This Useful Post: | ||
|
|
2014-12-27
, 01:34
|
|
Posts: 205 |
Thanked: 389 times |
Joined on Nov 2009
|
#52
|
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.
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.
 |
|
2014-12-27
, 11:59
|
|
Posts: 548 |
Thanked: 562 times |
Joined on Aug 2011
@ Germany
|
#53
|
Originally Posted by synt
I also tweaked this value now and it seems to work quite well till now.
The only tweak I've made is to increase vm.swappiness to 60 in /etc/sysctl.d/vm.conf file.
BTW if someone doesn't follow the TJC thread - a Jolla employee just posted an comment:
Originally Posted by tigeli
Maybe someone could provide some nice values for fine tuning. 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.
__________________
Nokia N80 -> Nokia N900 -> Nokia N9 -> Jolla Phone & Jolla Tablet -> Sony Xperia XA2 (SFOS)
Nokia N80 -> Nokia N900 -> Nokia N9 -> Jolla Phone & Jolla Tablet -> Sony Xperia XA2 (SFOS)
 |
|
2014-12-27
, 12:55
|
|
Posts: 764 |
Thanked: 2,888 times |
Joined on Jun 2014
|
#54
|
If you want something added to the Utilities to change OOM stuff: https://github.com/sailfishos/sailfish-utilities
| The Following User Says Thank You to nthn For This Useful Post: | ||
|
|
2014-12-29
, 02:11
|
|
Posts: 205 |
Thanked: 389 times |
Joined on Nov 2009
|
#56
|
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
"echo "0,0,0,0,0" > /sys/module/lowmemorykiller/parameters/minfree"
from https://together.jolla.com/question/...#comment-73891
 |
|
2014-12-29
, 02:58
|
|
Posts: 1,055 |
Thanked: 4,107 times |
Joined on Oct 2009
@ Norway
|
#57
|
Originally Posted by ste-phan
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.
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?
__________________
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
| The Following 14 Users Say Thank You to w00t For This Useful Post: | ||
aegis, eekkelund, Jordi, juiceme, Manatus, mariusmssj, mattaustin, minimos, Nekron, OVK, rcolistete, salyavin, sbock, Wikiwide | ||
|
|
2014-12-29
, 03:09
|
|
Posts: 1,055 |
Thanked: 4,107 times |
Joined on Oct 2009
@ Norway
|
#58
|
Originally Posted by m4r0v3r
The problem is that everyone is not you. Different people use their devices in different ways, run different software, emphasize different features.
I used to have issues with lag at times, but nothing to serious the device would stop functioning.
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
__________________
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
|
|
2015-07-14
, 01:50
|
|
Posts: 2,076 |
Thanked: 3,268 times |
Joined on Feb 2011
|
#59
|
Originally Posted by salyavin
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.
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
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
thanks to nieldk
Last edited by szopin; 2015-07-14 at 18:35.
|
|
2017-03-20
, 11:31
|
|
Posts: 83 |
Thanked: 91 times |
Joined on Nov 2015
@ NIgeria
|
#60
|
Originally Posted by szopin
This commands might have worked previously but on 2.0.5.6 I still get apps being killed and some lagging behavior at times.
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:
your process will die if it eats all swap+ram, but other apps stay aliveCode:echo '9999' > /sys/module/lowmemorykiller/parameters/adj echo '1' > /sys/module/lowmemorykiller/parameters/minfree
thanks to nieldk
What are the commands to revert this please?
__________________
Sony C6 > Sony Ericsson K310 > Sony Ericsson K750 > N70 > N73 > N81 > N82 > N79 > E7 > N9 > Jolla
Sony C6 > Sony Ericsson K310 > Sony Ericsson K750 > N70 > N73 > N81 > N82 > N79 > E7 > N9 > Jolla
