kern.sched.quantum: Creepy, sadistic scheduler

Eugene Grosbein eugen at
Wed Apr 18 21:16:34 UTC 2018

19.04.2018 0:59, Peter wrote:

>   thank You very much for Your commenting and reports!
> From what I see, we have (at least) two rather different demands here:
> while George looks at the over-all speed of compute throughput, others are concerned about interactive response.
> My own issue is again a little bit different: I am running this small single-CPU machine as my home-office router, and it also runs a backup service, which involves compressing big files and handling an outgrown database (but that does not need to happen fast, as it's just backup stuff).
> So, my demand is to maintain a good balance between realtime network activity being immediately served, and low-priority batch compute jobs, while still staying responsive to shell-commands - but the over-all compute throughput is not important here.
> But then, I find it very difficult to devise some metrics, by which such a demand could be properly measured, to get compareable figures.

I run similar system (AMD Geode 500Mhz i386-compatible) and found that
SCHED_4BSD does it just fine without any additional non-default configuration:
no other kernel options (*PREEMPT*), no loader.conf/sysctl.conf tuning.

More information about the freebsd-stable mailing list