4 ms·
A full build at work generates over 200GB of output, and that's before considering things like intermediate writes to the page file or temporary files. The cod
by slededit 10y ago
A full build at work generates over 200GB of output, and that's before considering things like intermediate writes to the page file or temporary files.
The codebase is very large so this is unusual, but its not a trivial concern for people with large workloads. I imagine video editors have disk usage of a similar magnitude.
- hcarvalhoalves 10y ago> A full build at work generates over 200GB of output Impressive.