2026-10-26 21:58 UTC
github runners
10 year old cpu
target dir size
Although I’m not too sure about the state of github runners, these don’t have to do with ram (the cause for OOM and likely the freezing) and 3G for the target dir is VERY tame for a debug build
Replies (1)
-
@badmin@lemmy.today 2026-10-27 03:31
It was a release build just to be clear. Debug builds twice as fast (they have a custom profile with opt-level = 1) and indeed uses a lot more disk space. ram I just did a release build with –jobs=1, while measuring total RES memory of the cargo process tree. Number of pids ranged from 1 (just cargo, obviously) to 8, and max RES memory was ~3471MiB. So not too lightweight, but not buck breaking either. People just have unrealistic expectations. Developers could optimize the compiler for memory usage, but that would make the compiler actually slower. And who would be the target audience of such optimizations? People who want to build big Rust projects on Raspberry Pi Zero?