feature request: track resource usage on builds (peak memory, etc.)
This may be better suited for the day-to-day build infrastructure that needs to be written, but I'd like to suggest tracking resource consumption.
For example, do we know what is the minimum amount of RAM a machine needs to have to build packages? I discovered today that system/nss
requires more than 2GB (or to have swap), otherwise the OOM killer will intervene.
We could track disk, network, entropy, and CPU statistics to see where builds spend most of their time: Track clock and CPU time in fetch, unpack, prepare, build, check, and package.
Also track environment, things like the output of locale
, ulimit
, etc.