April 27, 201016 yr Author Commented the tunables out and restarted seems to have helped.. I just don't know enough about those values..
April 27, 201016 yr Commented the tunables out and restarted seems to have helped.. I just don't know enough about those values.. So, just to make sure, you commented out something that wasn't there when you first reported the problem and that solved the problem. If that is true, then you've just invented the universal fix for any problem! I do hope it's true.
April 28, 201016 yr Author Commented the tunables out and restarted seems to have helped.. I just don't know enough about those values.. So, just to make sure, you commented out something that wasn't there when you first reported the problem and that solved the problem. If that is true, then you've just invented the universal fix for any problem! I do hope it's true. I consider these tunables: sysctl -w vm.min_free_kbytes=8192 # sl:2497 sysctl -w vm.dirty_expire_centisecs=900 # sl:3000 tm:100 sysctl -w vm.dirty_writeback_centisecs=300 # sl:500 tm:50 sysctl -w vm.dirty_ratio=20 # sl:10 tm:10 sysctl -w vm.dirty_background_ratio=10 # sl:5 tm:5 These tweaks remain: for i in /sys/block/[hs]d? ; do echo 128 > $i/queue/max_sectors_kb ; done 2>/dev/null for i in /sys/block/[hs]d? ; do echo cfq > $i/queue/scheduler ; done 2>/dev/null
Archived
This topic is now archived and is closed to further replies.