About

Born at planetary scale

rusty started as an internal tool at iResolved, LLC — built while shipping client work on a Cargo workspace that cargo could not keep up with.

Origin

The project that forced the issue was a planetary-scale Rust monorepo: a Cargo workspace with 3,676 crates whose full cold compile took on the order of ~10 hours.

Day-to-day development was no better. Incremental compiles of that workspace still sat around ~6 hours — long enough that the edit–build–test loop effectively stopped existing.

rusty was written to fix that. A content-addressable store, native resolve/fetch/build paths, and a Linux-first toolchain — all aimed at making monorepos of that size feel local again.

Results on that workspace

  • Cold build

    ~10 hours

    ~10 min

    No downloaded deps, no cache

  • Dev compiles

    ~6 hours

    ~45 sec

    Routine workspace builds

  • Peak speedup

    ~400×

    Faster than cargo at routine tasks

Those numbers are from the client workspace that motivated the project — not a micro-benchmark. rusty can be up to ~400 times faster than cargo at routine tasks when the monorepo shape and cache hit the path it was built for.