Freeing Up Gigabytes: Reclaiming Disk Space from Rust Cargo Builds (thisdavej.com)
from thisdavej@programming.dev to rust@programming.dev on 25 Apr 01:07
https://programming.dev/post/29194739

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

#rust

threaded - newest

Kissaki@programming.dev on 25 Apr 10:23 next collapse

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 on 25 Apr 16:58 collapse

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 on 25 Apr 17:00 collapse

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

onlinepersona@programming.dev on 25 Apr 17:05 next collapse

Or, put target in RAM with cargo-ramdisk. Just don’t get yourself an overpriced Mac and pay for extra RAM instead. Save your SSD, stop worrying about rust clutter at the same time, and give a company money that won’t lock you in and give your money to Trump. Win win win.

Anti Commercial-AI license

QueenMidna@lemmy.ca on 25 Apr 17:11 collapse

I’ve been making extensive use of kondo to do my cleanup for me