Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
cargo-sweep can do this kind of garbage collection along a few axes - rustc version, file age, was or wasn't used during recent build. Works great on Linux. I've not gotten it working reliably for -s/-f on MacOS+APFS, but for the CI use case it should be a nice improvement.
Have you tried https://github.com/rui314/mold ? Claims to be significantly faster than lld.
Other than that, the performance of both for builds should be determined exactly by the organization of code into separate crates and the rustc invocations. Bazel generally encourages smaller crates, but that's very subtle. There is at least 1 case I can think of where rustc is overfit to cargo, in a way that is not easily replicable by bazel, which is the metadata/rlib pipelining https://github.com/bazelbuild/rules_rust/issues/228
I agree with you that the tutorial is incomplete, but I don't get what you're trying to say. Did you link the wrong thing? That is the CI for cargo-chef (as opposed to a CI setup with cargo-chef), which, unsurprisingly, doesn't use cargo-chef.
Related posts
- Rust Tooling: 8 tools that will increase your productivity
- Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
- Reddit temporarily ban subreddit and user advertising rival self-hosted platform (Lemmy)
- Exploring the problem of faster Cargo Docker builds
- 87% of Container Images in Production Have Critical or High-Severity Vulnerabilities