View Single Post
Posts: 669 | Thanked: 433 times | Joined on May 2010
#234
Originally Posted by vi_ View Post
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
  1. 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.
  2. 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 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.

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.
 

The Following 2 Users Say Thank You to impeham For This Useful Post: