cargo-chef
cargo-sweep
cargo-chef | cargo-sweep | |
---|---|---|
18 | 9 | |
1,526 | 673 | |
- | - | |
7.2 | 6.6 | |
22 days ago | about 1 month ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cargo-chef
-
Transitioning to Rust as a company
CI time. Do you want to micromanage your own docker images for all your CI? Great! If not, yes you do. In fact, you want to manage a docker image to build a docker image to use for CI. Use cargo-chef to prepare a build image with your dependencies pre-built if you want to do fine-grained build/test pipelines. Oh also, there's no jUnit test report generation, that was killed off today. (YES, SORRY, I'm still salty.)
-
Rust and Next.js everywhere?
Have you looked at cargo-chef? It supposedly speeds up compilation times if you're using Docker.
-
Exploring the problem of faster Cargo Docker builds
A tool already exists for this called Cargo-chef, and it works extremely well.
-
Deploying Rust APIs | What Is Your Favorite Method?
At work I've use Dockerfile and cargo-chef to improve build times. You can also look into buildkit cache mounts, but this approach is rarely super effective on hosted CI because they start from scratch on most runs. In the context of Rust specifically you may also see the target directory reflect unbounded data growth if it's reused over and over across revisions. because cargo by default won't expire older intermediate artifacts. Cargo-sweep can help with that but I wouldn't pursue this in a CI effort. This will affect both "native" builds and buildkit cache mounts if you're persisting the target directory.
-
How to write a GitHub Action in Rust
We create an empty Rust binary with cargo new, this is a simple way to get Docker layer caching to work. For a more robust solution, you may want to check out cargo-chef.
-
Crafting container images without Dockerfiles
If this ends up being a cleaner/easier way to having to workaround super expensive rebuilds for Rust given cache + deps compared to this https://github.com/LukeMathWalker/cargo-chef , reading this thread will have been a huge win for me (and hopefully others).
Whether introducing Bazel is easier/worth it, subjective I guess.
-
Is it possible to get fast Rust compiles in a Docker container?
I did a talk (slides here) about this a few years ago, it took a bit of work to get the build caching working with cargo. As others have pointed out, there is now cargo chef to solve this problem so you probably don't have to deal with the issues I saw, but I thought it still might be helpful context.
-
Faster CI builds for Rust with pre-baked builder images and sccache
I'm curious if you've tried out cargo-chef, I've had some decent improvements with it but I wonder how it stacks up to the sccache approach (don't have the time to try it out myself right now).
-
2 years of fiddling with Rust – critical thoughts
for CI have you tried to use buildkit persistent runners with caching + https://github.com/LukeMathWalker/cargo-chef ?
-
How to speed up the Rust compiler in July 2022
If you're deploying Rust with Docker I can tell you that cargo-chef is invaluable. With zero work it caches the dependency fetch and compilation steps. Most of the time the ens Docker deploy is closer to an incremental compile than full.
cargo-sweep
-
Target file are very huge and running out of storage on mac.
You can use cargo sweep or kondo to clean up unused files.
-
What are some useful tools for Rust?
cargo-sweep
-
crates.io now has more than 100,000 crates!
[1]: https://github.com/holmgr/cargo-sweep
-
Cargo Clean All - A cargo plugin to clean all your projects at once with filters
I use https://github.com/holmgr/cargo-sweep which can keep files from the current compiler version, but delete files from earlier compilers that won't ever be used again.
-
Announcing cargo-cleanall
How is this different from https://github.com/holmgr/cargo-sweep ?
-
Is this normal? Giant debug folder
I like https://github.com/holmgr/cargo-sweep to keep the size of /target from unbounded growth without fully losing the useful portion of the cache. It's the same outcome as Cargo clean after a reboot but I recently also started using a ramdisk with CARGO_TARGET_DIR. Much easier to do on Linux.
- Cargo clean for a number of projects
-
Blog Post: Fast Rust Builds
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.
-
STOP DOING RUST
holmgr is a god and cargo-sweep is a godsend
What are some alternatives?
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
rules_rust - Rust rules for Bazel
cargo-clean-all
mold - Mold: A Modern Linker 🦠
kondo - Cleans dependencies and build artifacts from your projects.
bloom - The simplest way to de-Google your life and business: Inbox, Calendar, Files, Contacts & much more
squatternaut - A snapshot of name squatting on crates.io
monadium - A platform with the purpose to teach Rust web development to people with no prior experience of programming
cargo-hack - Cargo subcommand to provide various options useful for testing and continuous integration.
football-simulator - Football simulation engine (like Football Manager) written in pure Rust
proc-macro2