3 ms·
This is the job of your operating system's scheduler - to divide the limited resource of your computer's CPU time among different competing tasks. In the moder
by rhencke 9y ago
This is the job of your operating system's scheduler - to divide the limited resource of your computer's CPU time among different competing tasks.
In the modern era, a program cannot take more than its fair share of CPU time - otherwise, a runaway program could easily render your computer nearly unusable. (Linux, macOS and Windows all use preemptive multitasking.)
The way to tell your operating system what you desire prioritized is, on *nix systems, 'nice'.
- taeric 9y agoI'm well aware of that. I also know that, in general, having to schedule things slows them down. If everything I'm running is trying to schedule something on my entire machine, it is giving my OS more work. Which will, by necessity, be harder to schedule and slow things down. I'm not necessarily against all of this, but I'm also not eagerly embracing more crap to slow down my machine for no apparent reason.
- demarq 9y agoYou are assuming that your OS scheduler is nearly at capacity, it isn't. And moreover your CPU is will spend most of it's life idle. I could almost guarantee you this is not the bottleneck of any modern setup.
- taeric 9y agoI can guarantee you that I have jumped over to my browser when doing a compile that is definitely limited by my machine. I'm ok doing this knowing that I will only take up so much work on my machine. I do not go off and kick off another giant compile at the same time. Now, if the browser becomes more and more consuming, hitting my browser could get closer and closer to kicking off another giant compile.