I noticed that my
target dir is over 100 GB in size again. That's more than double the size of all crates on crates.io, which seems unreasonable. Are we doing anything wrong? Is this because we update dependencies so often?
That and I think running tests on only some sub crates specifically(via
-p crate) cause some dependencies to recompile due to feature flags, at least I tend to see some stuff recompile depending on what crate I run tests on. But I'm not entirely sure on that one, might be misremembering.
are u regularely running cargo clean? cargo doesn't seem to cleanup when you eg. update your toolchain or when it has to recompile stuff
cargo test, and
cargo build --release (part of my usual workflow), my
target dir is only at 5.2G, so 100 certainly seems excessive.
heh, and that's with debug = 0...
Mine currently sits at 32gb :sweat_smile:
Could it be the incremental dir?
target/debug/incremental sits at 20gb for me
rm -rf library -- finally got my 12 core ryzen :D
oh nice, 5900X?
I now hate serde -- it's a sequential bottleneck
I'm already back up to 39 GB now
I wonder why these are duplicated?
why does the hash keep changing?
that normally happens when the crate version differs, the Rust version used to build it differs, or a different cargo profile was used
but I don't really expect it to crate so many versions during normal development
@Jonas Schievink looks like that if you update dependency, the hash changes
ie, updating rowan dupes every rust-analyzer crate
oh, that makes sense