#Build chews through 50G of disk to produce 3G image

1 messages · Page 1 of 1 (latest)

hearty mirage
#

the trace is not that long, not sure what is doing it

#

the first two go language downloads and installs are the one's I described as happening in parallel, if only the printing, unclear. The third one ran independently, which I expected to cache. This was a fresh run on a fresh engine, to verify this trace alone produces 50G of disk usage

#

It's probably why I saw cache thrashing, upped the disk to 100G, and was ok for a short while before the GC probably kicked back in and I saw cache thrashing again

#

also, disk usage is the other top complaint complaint I hear from the developers I have using dagger (the othesr being weirdness/slowness by comparison to non-containerized builds)

hearty mirage
#

ok, another test, loading up a 2.29GB image with my local monorepo, using the gitignore setting, uses 16G of disk

hearty mirage
#

ok, narrowed this down to an engine config issue, same dagger engine, different config (missing a volume I think is the underlying issue)