![]() ![]() Or if you don't know the answer, step back. The guy asked you a question, you can ask him what he is trying to achieve, but don't tell him what he should and shouldn't do, just answer the fucking question. So i guess that's what the guys at the linux kernel see as optimal for scheduling, I will take that as an answer.Ī little meltdown here, I hate these answers, such useless answers belongs to the most useless people in the world. Performance of BFS to other schedulers." - Brain Fuck Scheduler. It is worth noting this fact when comparing the latency It is based on the fact that humans can detect jitter atĪpproximately 7ms, so aiming for much lower latencies is pointless under mostĬircumstances. The default value of 6 is not anĪrbitrary one. Minimise the effect the Hz limitation has. "BrainFuck Scheduler uses "dithering" to try and Kolivas predicts a common case of between zero and two running tasks per CPU and, in such a scenario, a task will need to wait no longer than 6ms to get service." The reason for this is the threshold for human perception of jitter is just under 7ms. "The rr_interval tunable is set at 6ms by default. The linux kernel uses for both Completely Fair and brainfuck-scheduler/MuQss, 144 fps, and that's what x11 and wayland/weston windows managers respect (Confirmed, MuQss quantum duration is 6ms for all tasks with the same priority (1/144 = 6.9444e-3) 240hz monitor can be used for stereo-vision. 60, 90, 100, 120, 144Hz but could argue on the technical limitation of the human eye (if there is one) but I won't go there as I don't go there since my monitor is 60Hz. Why one would want a 240Hz monitor is beyond me. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |