I suppose it's not the worst problem to have. Makes me realize how spoiled I got after multiple-core computers became the norm.
I suppose it's not the worst problem to have. Makes me realize how spoiled I got after multiple-core computers became the norm.
[0]: https://www.gnu.org/software/make/manual/html_node/Job-Slots...
[2]: https://github.com/rust-lang/cargo/issues/1744
[2]: https://github.com/rust-lang/rust/pull/42682
`nice cargo build` will run all threads at low priority, but this is generally a good idea if you want to prioritize interactive processes while running a build in the background.
See https://github.com/rust-lang/cargo/blob/master/CHANGELOG.md#...
SMT is a throughput thing, and I honestly turn it off on my workstation for that reason. It's great for cloud providers that want to charge you for a "vCPU" that can't use all of that core's features. Not amazing for a workstation where you want to chill out on YouTube while something CPU intensive happens in the background. (For a bazel C++ build, having SMT on, on a Threadripper 3970X, does increase performance by 15%. But at the cost of using ~100GB of RAM at peak! I have 128GB, so no big deal, but SMT can be pretty expensive. It's probably not worth it for most workloads. 32 cores builds my Go projects quickly enough, and if I have to build C++ code, well, I wait. ;)
Make it a shell script like `takeiteasy`, and run `takeiteasy cargo ...`
dude cargo ...
has a nice flow to it.