nikon/tuned
1
0
Fork 0
Code Activity Actions

further throughput-performance profile tweaks

Browse source 
- don't set pid_max by default, as it can be highly dependent on cpu
  count (and architecture, to some extent)
- add commented out vm.dirty_background_ratio param, which we may or may
  not set sometime in the future, but its also there now for people to
  enable w/relative ease.

Signed-off-by: Jarod Wilson <jarod@redhat.com>
This commit is contained in:
Jarod Wilson 2010-07-14 11:21:30 -04:00
parent 53442a48af
commit 927529c1cc
1 changed files with 12 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
tune-profiles/throughput-performance/sysctl.ktune
View file

@ -16,9 +16,20 @@ kernel.sched_wakeup_granularity_ns = 15000000
# working set is buffered for I/O, and any more write buffering would require
# swapping, so it's time to throttle writes until I/O can catch up. Workloads
# that mostly use file mappings may be able to use even higher values.
#
# The generator of dirty data starts writeback at this percentage (system default
# is 20%)
vm.dirty_ratio = 40
# Start background writeback (via writeback threads) at this percentage (system
# default is 10%)
#vm.dirty_background_ratio = 15
# PID allocation wrap value. When the kernel's next PID value
# reaches this value, it wraps back to a minimum PID value.
# PIDs of value pid_max or larger are not allocated.
kernel.pid_max = 131072
#
# A suggested value for pid_max is 1024 * <# of cpu cores/threads in system>
# e.g., a box with 32 cpus, the default of 32768 is reasonable, for 64 cpus,
# 65536, for 4096 cpus, 4194304 (which is the upper limit possible).
#kernel.pid_max = 65536