OP
- Thread Starter
- #26
To sum up the first day of discussions in this thread.
The value suggested in most guides 223 is to high. My suspicion is that it is a value suggested quite early in the development of the ULE scheduler. On my system lowering the value has actually lowered the cpu temperature quite a bit. So using the resources more efficient, and reducing cpu load (and thereby improving interactivity more than a higher value). We are currently considering the following values for a interactive desktop system:
kern.sched.preempt_thresh=151 Time-share threads in interactive category
kern.sched.preempt_thresh=171 Time-share threads in batch category with nice priority between -1 and -20
kern.sched.preempt_thresh=162 as a middle ground between the two
On servers these values is not recommended. Mostly for desktops.
I might suggest that one or more of these values will be placed in the handbook as a part of tuning with sysctl.conf
Comments much appreciated.
Have a nice day
The value suggested in most guides 223 is to high. My suspicion is that it is a value suggested quite early in the development of the ULE scheduler. On my system lowering the value has actually lowered the cpu temperature quite a bit. So using the resources more efficient, and reducing cpu load (and thereby improving interactivity more than a higher value). We are currently considering the following values for a interactive desktop system:
kern.sched.preempt_thresh=151 Time-share threads in interactive category
kern.sched.preempt_thresh=171 Time-share threads in batch category with nice priority between -1 and -20
kern.sched.preempt_thresh=162 as a middle ground between the two
On servers these values is not recommended. Mostly for desktops.
I might suggest that one or more of these values will be placed in the handbook as a part of tuning with sysctl.conf
Comments much appreciated.
Have a nice day