4 ms·

Are both cases compiling to the same target architecture? If not, you may well be comparing the relative performance of different compiler backends instead of c

Are both cases compiling to the same target architecture? If not, you may well be comparing the relative performance of different compiler backends instead of comparing the performance of your CPUs. (+ now I see it's rust: how parallel is your build, really?)

gameswithgo 5y ago
that the arm backend is faster to compile for is a legit advantage for the developer though, even if its distinct from cpu perf
ripley12 5y ago
> now I see it's rust: how parallel is your build, really? Not the OP but I install a lot of Rust projects with Cargo and recently did some benchmarking on DigitalOcean's compute-optimized VMs. Going from 8 cores to 32 cores was a little disappointing: Bat (~40 crates): 68s -> 61s Nushell (486 crates): 157s -> 106s Compilation starts out highly parallel and then quickly drops down to a small number of cores.
kiratp 5y ago
The target arch doesn’t matter for the change-build-test loop d vs do. All that matters is how fast can you compile your code to test it. If the final x86 production build takes longer it doesn’t matter - that happens on the cloud anyway. Edit: Rust builds are very parallel until linking. No different than any other LLVM build.
- runeks 5y ago
  > The target arch doesn’t matter for the change-build-test loop d vs do. It matters when comparing CPU performance, which is what this benchmark is being used for.