If you’d a like a non-vibe coded astrological scheduler, I made one years ago for April Fools: https://github.com/razorpay/shubhcron I had to research silly Vedic nonsense on Hinduism stackexchange. While this one changes how your CPU behaves (and does not believe in the stars to do it for you), shubhcron waits for the right auspicious time to run your cronjobs (or other processes).
Very cool! I am guessing you never got around to making the Kubernetes controller you mention in the README? :D
Nopes, the packaging took up the last of my time for the project.
This scheduler takes advantage of sched_ext which is a relatively recent kernel capability. I really thought that EEVDF was the last word on scheduling in Linux, at least for the short-medium term. Apart from trolling I am really curious what other useful functionality sched_ext enables. One of the primary reasons CFS was replaced with EEVDF was because it has a better set of defaults which don't require tuning / pat…
the main reason why sched_ext is taking off is that EEVDF and CFS before it are -general- cpu schedulers, so while they work well for most tasks, they don't work as well as they could in certain situations like heavy server loads, low-latency loads (like multimedia production and gaming), or security sensitive loads. These schedulers are built and or specifically tunable to these types of loads, such as scx_lavd, scx_bpfland, and scx_cosmos. They each approach things differently, such as using core compaction, sharing or unsharing per core task queues, being way more cache context aware, keeping hot cores hot, etc. And the perf boost in these specific contexts is very real. Heck, Meta started using scx_lavd for better task load balencing over EEVDF on their servers.
If you’d a like a non-vibe coded astrological scheduler, I made one years ago for April Fools: https://github.com/razorpay/shubhcron I had to research silly Vedic nonsense on Hinduism stackexchange. While this one changes how your CPU behaves (and does not believe in the stars to do it for you), shubhcron waits for the right auspicious time to run your cronjobs (or other processes).
Can the "vibe" statement be substantiated in any way? Also your "scheduler" is in a completely different domain, it doesn't even remotely relate.