You should have set up https://github.com/mozilla/sccache at minimum. Setting up compiler caching is routine for people coming from older compiled language backgrounds but it's often missed by people coming from languages like JS/TS who have never been exposed to these ideas.

There's a new project called kache https://github.com/kunobi-ninja/kache that takes this even further and handles more edge cases with worktrees, but it's newer.

If you were pulling the entire project fresh and rebuilding everything in every worktree all the time without any caching then it would be frustrating. You could have asked your agent to set up basic caching and solved most of your problem in minutes.

You really shouldn't build software with rust if your workflow involves 10+ agents. Why aren't you using Python or Typescript for things like that?

Rust is what you use when you want to maximize on the runtime performance. It will build software that requires significantly less memory and maximize the CPU that will save time and energy. It's a system language for writing software meant to access the hardware.

Most of that time was probably compiling dependencies. If you give it another go, I would recommend a shared sccache.

https://github.com/mozilla/sccache

Make a cargo wrapper (or ask your clanker) with a global build lock.

Cargo run/test/nextest/run only, check/fmt etc should be excluded.

This avoids contention/oversubscription of the CPU which makes builds up to 300% slower from what I measured.

first time i've seen rust's compile performance actually act as a filter haha

[flagged]