poe-stash-indexer VS sccache

Here is a pipeline when the cache was missed due to GitHub cache eviction, so a fresh build. Here is a pipeline when the cache was hit.

Wrt #2: I use VSCodium with manually installed extensions as well. In my shell.nix I have cargo and rusr-analyzer as build inputs and I start the editor from within the nix shell via nix-shell && code . which works fine. Here is my config , but maybe I misunderstood your problem.

IIRC the single most effective thing for my CI setup was using mold as a linker. There are good resources on the web on how to set that up. This is what I did for my docker builds.

as mentioned in my post a few weeks ago, I am running my public trade API service for Sentinel league as well.

All API documentation and further info can be found on this GitHub repository. I plan on running this during the upcoming challenge leagues as well.

I also use alpine to run my app, maybe this Dockerfile helps you link.

Already some good comments there, but here is how I did it recently.

Worth noting that the first commit in sccache git repository was in 2014 (https://github.com/mozilla/sccache/commit/115016e0a83b290dc2...). So I suppose that what "happened" happened waay back.

If you have lots of shared dependencies, maybe try sccache?

I'm going to set up sccache [0] to use it tomorrow. We use MSVC, so EFS is off the cards.

[0] https://github.com/mozilla/sccache/blob/main/docs/S3.md

I think the primary benefit of pre-built procmacros will be for build servers which don't use a persistent cache (like sccache), since they have to compile all dependencies every time. But IMO improved support for persistent caches would be a better investment compared to adding support for pre-built procmacros.

Checkout https://github.com/mozilla/sccache

https://github.com/mozilla/sccache is another option which addresses the use cases of both icecream and ccache (and also supports Rust, and cloud storage of artifacts, if those are useful for you)

That being said a compilation cache, eg the de-facto standard for Rust: sccache (https://github.com/mozilla/sccache) will help to compile and store some of the build artifacts centralized - still for each crate version + build profile (RUSTFLAGS) combination.

That's definitely not my experience. Never had any issue running Rust on Windows. You just download and run rustup-init.exe, then updating is simply a matter of rustup update. Documentation generation is built in (cargo doc) and just a case of annotating code with triple-/ markdown comments and then running that command. sccache works fine for me (just need to set RUSTC_WRAPPER=/path/to/sccache). And the error messages from rustc are by far the best of any compiler I've used. Not sure how they're unhelpful, they tend to explain step-by-step what the problem is and how to fix it.