```
> cargo clean && time cargo build
cargo build 713.80s user 91.57s system 706% cpu 1:53.97 total
> cargo clean && time cargo build --release
cargo build --release 1619.53s user 142.65s system 354% cpu 8:17.05 total
this is without incremental compilation. And it's not like you have to babysit a release build if you have a CI/CD system
https://corrode.dev/blog/tips-for-faster-rust-compile-times/...
FWIW - last stage where the binary is produced takes the longest and is single threaded and that's the largest difference between release and debug.
At a quick glance, most benchmarks show only 50% to 60% single threaded improvement between M1 and M4.
That wouldn't explain compilation times going from 6 minutes to 2 minutes.
```
> cargo clean && time cargo build
cargo build 713.80s user 91.57s system 706% cpu 1:53.97 total
> cargo clean && time cargo build --release
cargo build --release 1619.53s user 142.65s system 354% cpu 8:17.05 total
```
this is without incremental compilation. And it's not like you have to babysit a release build if you have a CI/CD system