- This is a pretty funny project, you've outsourced the neurotic developers that keep their task manager open and kill off processes they don't like.
I wouldn't call it replacing the scheduler though - more that you've made a scheduler manager.
- OP here. this is a cursed project lol, but i wanted to see: What happens if you replace the OS scheduler with an LLM?
With Groq speed (Llama 3 @ 800t/s), inference is finally fast enough to be in the system loop.
i built this TUI to monitor my process tree. instead of just showing CPU %, it checks the context (parent process, disk I/O) to decide if a process is compiling code or bloatware. It roasts, throttles, or kills based on that.
Its my experiment in "Intelligent Kernels" how they would be. i used Delta Caching to keep overhead low.
- It really is cursed to be spending hundreds of watts of power in a datacenter somewhere to make a laptop run slightly faster.
- You can't replace the NTOS scheduler. This is more of an automated (?) process manager.
- You're underselling this as a process manager, it could also be a productivity tool with some prompt changes; Determine procrastination apps: games, non-professional chat, video streaming and kill it.
- If it doesn’t find a process that needs roasting or killing for a while, will it see itself as bloatware and commit suicide?
- Please add Roulette mode where a random process is killed every so often
- Interesting experiment. Scheduling decisions feel like the place where unpredictability shows up first. Curious how you reason about rollback when the scheduler makes a bad call.
- You did not replace the OS process scheduler with an LLM.
- This is the one place that I would want Copilot running. It's giving me ideas :)
- Why not branch prediction with LLM?
- Please name it juggler
- Task manager, not scheduler.
- Ok