You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the CFS tuning happens when the option is enabled and what it does is switching between the two profiles when the power source is either battery or ac. However, there's no place in the config file where that information is stated:
// Latency profiles the kernel's Completely Fair Scheduler
cfs-profiles enable=true {
// The kernel-default values which are ideal for battery life and servers
default latency=6 nr-latency=8 wakeup-granularity=1.0 bandwidth-size=5 preempt="voluntary"
// Zen CFS parameters that make the desktop more responsive
responsive latency=4 nr-latency=10 wakeup-granularity=0.5 bandwidth-size=3 preempt="full"
}
Ideally, I'd swap the profile names default and responsive to battery and ac respectively, so they reflect better what the scheduler is actually doing. An alternative would be to simply add a comment making that clearer.
Would you be willing to accept patches for either?
The text was updated successfully, but these errors were encountered:
Agreed, I'm very confused by this section of the config. I'm also wondering if it's possible to switch the profiles, and how I might see which profile is currently in use.
If my machine is on AC and that makes it choose responsive, I'd love to know that's the case. A comment and README update would be enough.
Currently, the CFS tuning happens when the option is enabled and what it does is switching between the two profiles when the power source is either battery or ac. However, there's no place in the config file where that information is stated:
Ideally, I'd swap the profile names
default
andresponsive
tobattery
andac
respectively, so they reflect better what the scheduler is actually doing. An alternative would be to simply add a comment making that clearer.Would you be willing to accept patches for either?
The text was updated successfully, but these errors were encountered: