this post was submitted on 25 Apr 2025
22 points (100.0% liked)

Rust

6842 readers
2 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
EdTheLegendary@programming.dev
kahnclusions@programming.dev
torcherist@programming.dev
22
Freeing Up Gigabytes: Reclaiming Disk Space from Rust Cargo Builds (thisdavej.com)
submitted 2 days ago* (last edited 2 days ago) by thisdavej@programming.dev to c/rust@programming.dev
5 comments fedilink hide all child comments
 

This article delves into various techniques for reclaiming disk space from Cargo build artifacts.

you are viewing a single comment's thread
view the rest of the comments
[–] Kissaki@programming.dev 3 points 2 days ago (1 children)

I changed the cargo home/cache directory so it's easier to clean up. The disk space pollution of Rust is insane.

I did a small project project that resulted in an 8 MB executable. And had dozens of gigabytes to clean up.

Even more confusing was how closing VS Code lead to 11 GBs being freed. I initially had three or four projects open for reference in APIs and API usage. But my primary partition ran full quickly. In the end I used Rover and minimized IDE usage to two instances. And after my work, removed target and cargo build data again so I actually have space to work with on my primary partition.

[–] Tenkard@lemmy.ml 1 points 2 days ago* (last edited 1 day ago) (1 children)

I used to compile zed since there was no Linux binary back then, then I discovered the disk use was 90 GB :|

[–] corpsmoderne@mamot.fr 0 points 2 days ago

@Tenkard @Kissaki only ? That's a bargain 😬