Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 12 hrs, 48 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 1 hr ago - more...
BertvanDorp |
2012-05-29
, 21:10
|
|
Posts: 58 |
Thanked: 43 times |
Joined on Aug 2010
|
#231
|
I ran just SwapSet (without swap-to-SD), and noticed the tracker going down as well.
|
|
2012-05-29
, 21:25
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#232
|
Like I said this all a bit experimental right now. Anyway, the VM settings have been tweaked to:
I have been using the above with a 128MB ramz. Freemangordon (the coder behind this) calls this unsane and reccomends 64MB max.
Try for yourself, report back.
Last edited by vi_; 2012-05-29 at 22:22. Reason: changed some values
Code:
echo 3 > /proc/sys/vm/dirty_ratio echo 3 > /proc/sys/vm/dirty_background_ratio echo 100 > /proc/sys/vm/dirty_writeback_centisecs echo 100 > /proc/sys/vm/dirty_expire_centisecs echo 1024 > /proc/sys/vm/min_free_kbytes echo 95 > /proc/sys/vm/swappiness echo 250 > /proc/sys/vm/vfs_cache_pressure echo 0 > /proc/sys/vm/page-cluster echo 512 > /sys/block/mmcblk0/queue/nr_requests echo 512 > /sys/block/mmcblk1/queue/nr_requests echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle echo 0 > /sys/block/mmcblk1/queue/iosched/slice_idle echo 16 > /sys/block/mmcblk0/queue/iosched/quantum echo 16 > /sys/block/mmcblk1/queue/iosched/quantum echo 64 > /sys/block/mmcblk0/queue/iosched/fifo_expire_sync echo 64 > /sys/block/mmcblk1/queue/iosched/fifo_expire_sync echo 64 > /sys/block/mmcblk0/queue/iosched/fifo_expire_async echo 64 > /sys/block/mmcblk1/queue/iosched/fifo_expire_async
- Do not use old settings, the min_free_kb is too low and will cause insta-crash when launching camera. This possibly also responsibile for tracker crash, tracker is just more graceful about it.
- You ABSOLUTELY MUST remove all traces of swappolube.
I have been using the above with a 128MB ramz. Freemangordon (the coder behind this) calls this unsane and reccomends 64MB max.
Try for yourself, report back.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
Last edited by vi_; 2012-05-29 at 22:22. Reason: changed some values
| The Following 6 Users Say Thank You to vi_ For This Useful Post: | ||
|
|
2012-05-29
, 21:31
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#233
|
Originally Posted by mr_jrt
Yes it MUST overide swappolubes settings. They are the reason ramz performance was blowing goatz.
I'm the chappie who threw together swapset. I've tried the above settings with it and it works awesomely. The settings caused resets under load for me at first, but I realised I still had a very old set of settings in my /etc/default/kernel-power file, and after dumping those all seems well. I might try overclocking again to see if I can get the best of both world...but awesome job for that bit of tuning. I stopped looking at swapset when I realised compcache had awful performance with my current settings, but I might go back to it now and have it automatically swap between vm settings based upon whether you have compcache in use. Might have to add a conflicts with swapolube though...or perhaps just override it? Hmmm...
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
| The Following 3 Users Say Thank You to vi_ For This Useful Post: | ||
|
|
2012-05-29
, 23:19
|
|
Posts: 669 |
Thanked: 433 times |
Joined on May 2010
|
#234
|
Originally Posted by vi_
i removed swappolube and set these settings. i'll test this from tomorrow to see how it is - but i'll be using the 64mb swap instead of 128 - i think the 128 is too much since most of the time the device is already above 128.
Like I said this all a bit experimental right now. Anyway, the VM settings have been tweaked to:
Code:echo 3 > /proc/sys/vm/dirty_ratio echo 3 > /proc/sys/vm/dirty_background_ratio echo 100 > /proc/sys/vm/dirty_writeback_centisecs echo 100 > /proc/sys/vm/dirty_expire_centisecs echo 1024 > /proc/sys/vm/min_free_kbytes echo 95 > /proc/sys/vm/swappiness echo 250 > /proc/sys/vm/vfs_cache_pressure echo 0 > /proc/sys/vm/page-cluster echo 512 > /sys/block/mmcblk0/queue/nr_requests echo 512 > /sys/block/mmcblk1/queue/nr_requests echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle echo 0 > /sys/block/mmcblk1/queue/iosched/slice_idle echo 16 > /sys/block/mmcblk0/queue/iosched/quantum echo 16 > /sys/block/mmcblk1/queue/iosched/quantum echo 64 > /sys/block/mmcblk0/queue/iosched/fifo_expire_sync echo 64 > /sys/block/mmcblk1/queue/iosched/fifo_expire_sync echo 64 > /sys/block/mmcblk0/queue/iosched/fifo_expire_async echo 64 > /sys/block/mmcblk1/queue/iosched/fifo_expire_async
- Do not use old settings, the min_free_kb is too low and will cause insta-crash when launching camera. This possibly also responsibile for tracker crash, tracker is just more graceful about it.
- You ABSOLUTELY MUST remove all traces of swappolube.
I have been using the above with a 128MB ramz. Freemangordon (the coder behind this) calls this unsane and reccomends 64MB max.
Try for yourself, report back.
i've resolved the tracker issue - it seems that the problem was somehow related to queen beecon: i've created a new widget which the OS didn't seem to like and by removing it everything's ok now.
i'll check why this widget made a problem.
|
|
2012-05-30
, 07:13
|
|
Posts: 309 |
Thanked: 456 times |
Joined on Jan 2010
|
#235
|
Been trying trying settings for a couple of days, along with swap on SDcard partition.. It seems my N900 will reboot after a while when using SD swap - verified on stock kernel and SDswap only, may be due to the fact it is a 1st gen SANDisk 8Gb card and might not be fast enough, so I'm running tests using default eMMC swap and ramzswap.
Using 128mb cache the device was still responsive even during an update using HAM.. I now have it launched as an event.d script.
i will try the new settings and see how it goes, in particular if it affects battery life due to RAM usage instead of eMMC access.
Is it possible to launch this earlier in the boot process, as part of RCS_LATE?
Using 128mb cache the device was still responsive even during an update using HAM.. I now have it launched as an event.d script.
i will try the new settings and see how it goes, in particular if it affects battery life due to RAM usage instead of eMMC access.
Is it possible to launch this earlier in the boot process, as part of RCS_LATE?
 |
|
2012-05-30
, 07:23
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#236
|
Good morning.
Removed swappolube tuning file and all other settings, enabled ramzswap after (hint for DarkGunman
start on started ke-recv, loaded vi_'s settings.
AND GOT THIS AFTER A FEW MINUTES USING :
And this after/during writing this:
Also it is not as snappy as before.
Keep in mind that I have swap on a swap file on SD (mmcblk1p1).
I dont think this is sane and therefore I will wait for some more testers.
Removed swappolube tuning file and all other settings, enabled ramzswap after (hint for DarkGunman
start on started ke-recv, loaded vi_'s settings.AND GOT THIS AFTER A FEW MINUTES USING :
Code:
~ $ iostat -m
Linux 2.6.28.10-power50 (delite) 05/30/12 _armv7l_ (1 CPU)
avg-cpu: %user %nice %system %iowait %steal %idle
23.49 0.05 17.05 19.12 0.00 40.29
Device: tps MB_read/s MB_wrtn/s MB_read MB_wrtn
mmcblk1 84.34 2.02 0.21 2101 222
mmcblk1p1 84.33 2.02 0.21 2101 222
rootfs 137.96 0.15 0.00 157 2
log 0.19 0.00 0.00 0 0
config 6.93 0.00 0.00 0 0
mmcblk0 13.22 0.14 0.01 149 9
mmcblk0p1 0.85 0.01 0.00 15 0
mmcblk0p2 12.35 0.13 0.01 134 9
mmcblk0p3 0.01 0.00 0.00 0 0
rootfs 0.00 0.00 0.00 0 0
log 0.00 0.00 0.00 0 0
config 0.00 0.00 0.00 0 0
Code:
~ $ iostat -m
Linux 2.6.28.10-power50 (delite) 05/30/12 _armv7l_ (1 CPU)
avg-cpu: %user %nice %system %iowait %steal %idle
20.26 0.04 15.47 21.39 0.00 42.84
Device: tps MB_read/s MB_wrtn/s MB_read MB_wrtn
mmcblk1 102.14 2.21 0.18 3270 270
mmcblk1p1 102.14 2.21 0.18 3270 270
rootfs 116.65 0.13 0.00 193 2
log 0.13 0.00 0.00 0 0
config 4.87 0.00 0.00 0 0
mmcblk0 9.90 0.11 0.01 167 10
mmcblk0p1 0.59 0.01 0.00 15 0
mmcblk0p2 9.29 0.10 0.01 152 10
mmcblk0p3 0.01 0.00 0.00 0 0
rootfs 0.00 0.00 0.00 0 0
log 0.00 0.00 0.00 0 0
config 0.00 0.00 0.00 0 0
Keep in mind that I have swap on a swap file on SD (mmcblk1p1).
I dont think this is sane and therefore I will wait for some more testers.
|
|
2012-05-30
, 08:22
|
|
Posts: 58 |
Thanked: 43 times |
Joined on Aug 2010
|
#237
|
Ran the 'old' settings:
Device is still responsive after a day. Tracker runs, camera is able to launch (this didn't work with Swappolube settings and SwapSet), but now I'm getting the message that states I can't send or reviece messages: device memory full.
Trying new settings now. @mr_jrt: including in SwapSet would be great, since it's clearly the only way to get ramz to work properly. You can also set Swappolube as a conflicting package, so users have to choose (does this make sense?).
echo 3 > /proc/sys/vm/dirty_ratio
echo 3 > /proc/sys/vm/dirty_background_ratio
echo 100 > /proc/sys/vm/dirty_writeback_centisecs
echo 100 > /proc/sys/vm/dirty_expire_centisecs
echo 32 > /proc/sys/vm/min_free_kbytes
echo 95 > /proc/sys/vm/swappiness
echo 666 > /proc/sys/vm/vfs_cache_pressure
echo 0 > /proc/sys/vm/page-cluster
echo 4 > /sys/block/mmcblk0/queue/nr_requests
echo 4 > /sys/block/mmcblk1/queue/nr_requests
Trying new settings now. @mr_jrt: including in SwapSet would be great, since it's clearly the only way to get ramz to work properly. You can also set Swappolube as a conflicting package, so users have to choose (does this make sense?).
|
|
2012-05-30
, 09:12
|
|
Posts: 1,341 |
Thanked: 708 times |
Joined on Feb 2010
|
#238
|
Originally Posted by peterleinchen
Where did you get iostat for N900?
Code:~ $ iostat -m Linux 2.6.28.10-power50 (delite) 05/30/12 _armv7l_ (1 CPU)
dpkg --search `which iostat`
Edit: ah, apt-cache search iostat
-> sysstat
Last edited by zimon; 2012-05-30 at 09:15.
|
|
2012-05-30
, 10:02
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#239
|
Originally Posted by BertvanDorp
Not really such a great idea, what if someone is using uSD but not ramz and wants swappolube settings?
Ran the 'old' settings:
Device is still responsive after a day. Tracker runs, camera is able to launch (this didn't work with Swappolube settings and SwapSet), but now I'm getting the message that states I can't send or reviece messages: device memory full.
Trying new settings now. @mr_jrt: including in SwapSet would be great, since it's clearly the only way to get ramz to work properly. You can also set Swappolube as a conflicting package, so users have to choose (does this make sense?).
I would encourage everyone to only use these settings as a start point and try to find what is optimal for the n900. Also, DO NOT USE:
Code:
echo 32 > /proc/sys/vm/min_free_kbytes
Code:
echo 1024 > /proc/sys/vm/min_free_kbytes
A good source of info is this
Finally I would not be so hasty to add this to your start up unless you are comfortable with using a rescue console to undo what may go wrong.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
Last edited by vi_; 2012-05-30 at 10:05.
| The Following 4 Users Say Thank You to vi_ For This Useful Post: | ||
