Added cargo cache improvements 2025H2 goal #317
Conversation
| * Stabilize Cargo `build-dir` which allows users to move intermediate build artifacts out of `target` (rust-lang/cargo#14125) | ||
| * Rework the build directory layout so that we have more easily cacheable "units" (rust-lang/cargo#15010) | ||
| * Work towards a user wide build cache that can be reused across projects/workspaces. (rust-lang/cargo#5931) | ||
| * Explore possibilities of extending this build cache to support remote storage enabling continuous integration use cases. | ||
|
|
There was a problem hiding this comment.
Something we discussed today in the cargo team meeting is that this seems a little ambitious for a 6-month goal. I'm not sure what changes would be appropriate, but maybe @epage has some ideas.
There was a problem hiding this comment.
My thought was to scale this down to the build directory layout re-work + experiments with an alternative locking scheme to try to help with r-a today and inform the locking scheme we use on the shared cache.
There was a problem hiding this comment.
Sure, seems reasonable. I suppose nothing is stopping us from continuing towards the shared cache if things go quicker than expected.
I'll update this goal later this week.
There was a problem hiding this comment.
I scoped the goal down to just build dir layout and locking changes.
ranger-ross
force-pushed
the
better-cargo-caching
branch
from
8955102 to
38a88f5
Compare
src/2025h2/cargo-build-dir-layout.md
Outdated
| | Teams | <!-- TEAMS WITH ASKS --> | | ||
| | Task owners | <!-- TASK OWNERS --> | | ||
| | Status | Proposed | | ||
| | Tracking issue | *if this is a continuing goal, add the old tracking issue, else leave blank* | |
There was a problem hiding this comment.
As the line says, this needs to be blank.
| | Tracking issue | *if this is a continuing goal, add the old tracking issue, else leave blank* | | |
| | Tracking issue | | |
src/2025h2/cargo-build-dir-layout.md
Outdated
| | Metadata | | | ||
| |:-----------------|----------------------------------------------------------------------------------| | ||
| | Point of contact | @ranger-ross | | ||
| | Teams | <!-- TEAMS WITH ASKS --> | |
There was a problem hiding this comment.
| | Teams | <!-- TEAMS WITH ASKS --> | | |
| | Teams | <!-- TEAMS WITH ASKS --> | |
src/2025h2/cargo-build-dir-layout.md
Outdated
| |:-----------------|----------------------------------------------------------------------------------| | ||
| | Point of contact | @ranger-ross | | ||
| | Teams | <!-- TEAMS WITH ASKS --> | | ||
| | Task owners | <!-- TASK OWNERS --> | |
There was a problem hiding this comment.
| | Task owners | <!-- TASK OWNERS --> | | |
| | Task owners | <!-- TASK OWNERS --> | |
src/2025h2/cargo-build-dir-layout.md
Outdated
| * Fine grain locking within the build directory | ||
| * Reducing build dir lock contention between Cargo and Rust Analyzer |
There was a problem hiding this comment.
| * Fine grain locking within the build directory | |
| * Reducing build dir lock contention between Cargo and Rust Analyzer | |
| * Fine grain locking within the build directory | |
| * Reducing build dir lock contention between Cargo and Rust Analyzer |
ranger-ross
force-pushed
the
better-cargo-caching
branch
from
38a88f5 to
cddef88
Compare
5 participants
I'd like to revive the Cargo user wide cache project goal from 2024H2.
Many sections remain unchanged, but some have been updated as there was some progress towards this in 2025H1.
Rendered