maemo.org - Talk - Lagging Solutions for N9

maemo.org - Talk (https://talk.maemo.org/index.php)

- MeeGo / Harmattan (https://talk.maemo.org/forumdisplay.php?f=45)

- - Lagging Solutions for N9 (https://talk.maemo.org/showthread.php?t=90281)

Re: Lagging Solutions for N9

Quote:

Originally Posted by tortoisedoc (Post 1348923)

Might also depend on the battery level of each device - and / or battery qualiy?

Battery in slower testing one is in better shape and was at full charge. Faster results are from my main phone, so battery might have degraded a bit (not much though as it still charges nearly to the max.)

@Yisroel

Good. Nothing out of ordinary in CPU usage, but something seems to be hogging your RAM. Try to hit "m" key while running top and it will sort processes by highest memory usage. Maybe some app has a memory leak or has crashed and is still reserving RAM for itself.

You are also running some daemon called theshaketorchd in the background, which is using some CPU and RAM. Though if you find the app useful and haven't experienced too much of battery drain t's probably not a problem.

PS. While looking at this I also ran top on my own phone ane noticed that cutetube had crashed (I didn't have it open and I have disabled the cutetubed daemon) and hogging over 200MB of RAM. :)

To kill processes you have two ways. Using PID (process ID), which you can see from top or ps output. Or by using the name of the process.

Former is done with command "kill [PID]" and latter by command killall [name]. Both take flag -9 to force kill if the process doesn't respond. So for example:

Code:

$ killall -9 cutetube

Re: Lagging Solutions for N9

...or use 'kill -9 $(pidof process_name)' -- SIGHUP may be a better first try than forcekill.

here's what i got. is there anything that shouldn't be there? i don't wanna start killing processes without knowing what they are.

Code:

Mem: 712988K used, 295660K free, 0K shrd, 9740K buff, 197776K cached

CPU:  5.7% usr  0.9% sys  0.0% nic 92.4% idle  0.1% io  0.5% irq  0.0% sirq

Load average: 0.30 0.19 0.27 1/355 18672

  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND

14360     1 user     S <   228m 22.9  0.0 /usr/bin/meego-im-uiserver -remote-theme -u

10379   876 user     S     203m 20.5  0.0 /usr/bin/fenix -prestart

18471   876 user     S <   191m 19.3  0.0 /opt/forum-qml/bin/forum-qml --tmo

13206   876 user     S     189m 19.1  0.0 /usr/bin/call-history -prestart

16938   876 user     S     180m 18.2  0.0 /usr/bin/camera-ui -prestart

 1824   876 user     S     180m 18.2  0.0 /usr/bin/messaging-ui -prestart

16505   876 user     S     165m 16.6  0.0 /usr/bin/call-ui -prestart

  957     1 user     S <   163m 16.5  0.0 /usr/bin/meegotouchhome -remote-theme -upst

 2080   876 user     S     161m 16.2  0.0 /usr/bin/contacts -prestart

18058   876 user     S     155m 15.7  0.0 /usr/bin/grob -prestart

 1124     1 user     S     152m 15.3  0.6 /usr/bin/sysuid -graphicssystem meego

 2207   876 user     S     146m 14.7  0.0 /usr/bin/organiser -prestart

  931   876 user     S <   123m 12.4  0.0 /usr/bin/conndlgs

18561   876 user     S <   115m 11.6  0.0 booster-m

  933   876 user     S N   113m 11.3  0.0 /usr/bin/applifed.x

 1347     1 user     S N   112m 11.3  0.0 /usr/bin/msyncd

18626   876 user     S <   111m 11.2  0.0 booster-d

 1528  1385 user     S N   109m 11.0  0.0 msgindexer

 1629     1 user     S N   107m 10.8  0.0 /usr/bin/contactsd

 1762     1 user     S <   107m 10.8  0.0 /usr/bin/commhistoryd

  876     1 user     S <   104m 10.5  0.0 /usr/bin/applauncherd.bin --boot-mode

~ $

as for the shake torch it is very useful. it lets you turn on/off your torch flashlight just by shaking the phone even from the lock screen.

Re: Lagging Solutions for N9

Everything there looks normal. Now you have also more free memory (ca. 305MB) compared to your previous posting.

There also exists app called n9-button monitor, which lets you to use long press of volume keys to light the flash LED when the phone is idle. I haven't used that shaketorch app yet and I don't really know if polling accelometer is more resource intensive (just have a gut feeling it might be), but maybe someone with more knowledge can comment on that.

Other than that your N9 is probably as fast as it can be without overclocking. Even if this device is quite tweakable the hardware has its limits.

Also if swapping becomes a problem, then reducing systems tendency to swap *might help a little. I expect that you won't even notice the difference, but if you wish to try you can write some smaller value to /proc/sys/vm/swappiness (default if I recall correct is 25). Smaller value means that kernel will be more conservative in moving pages to swap. Values can range from 0 to 100.

Example:

Code:

~ # cat /proc/sys/vm/swappiness

10

~ # echo 1 > /proc/sys/vm/swappiness

~ # cat /proc/sys/vm/swappiness

1

~ #

Setting swappiness like above is not permanent and is in effect only until next reboot (then sysctl sets it to default value, which is defined in /etc/default/sysctl). As to what value works best for N9, no idea. I use 10 right now.

Re: Lagging Solutions for N9

Quote:

Originally Posted by ladoga (Post 1348903)

Bit off-topic, but the performance of N9's flash storage seems to vary quite wildly from N9 to another, Maybe Nokia aquired chips from several sources.

For example I have two N9's which give very different results using hdparm.:

You can check the output of dmesg and you will realize that you are correct. There are 2 chipsets being used in N9 and 3 camera modules too IIRC ;-)