Closed abright closed 1 year ago
Since this stuff only affects cargo downloading its index, it doesn't seem to have much impact on our build times. Most of the time is spent building the many dependencies we have and there's no easy solutions there. Some typical approaches are to run dedicated hardware or to go down the rabbit hole of building inside containers with pre-built and cached dependencies (and then automating that to update in step with Cargo.lock
, etc)
See https://blog.rust-lang.org/inside-rust/2023/01/30/cargo-sparse-protocol.html
Not sure if this will have much benefit for the way our CI builds, but it's worth testing to see if it does save a few minutes off the total runtime