poe-stash-indexer VS test-s3-direct-upload

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.

Something I'd like to point out, I was using Scaleway but their S3 was too slow. I switched to DigitalOcean after I benchmarked their S3 because it's cheap and super fast. It improved my building speed but I was still using gitlab registry, and starting new CI job would fetch those massive builder image (3GB compressed). I then switched to digitalocean registry to be "closer" from my runners using digitalocean droplets, and it massively improved the time to start new job when the docker image wasn't locally cached yet. I did a traceroute from my droplet to gitlab, it was only a few hop but it still improved a lot... So I guess you should make sure your docker registry, your S3 bucket, and your runners are all running on the same network.