#Not a dagger specific question but I was
oblique vortex
AFAIK buildkit was adding some support for resource tracking. cc @hollow pendant might know about it
hollow pendant
yup, this was being done in https://github.com/moby/buildkit/pull/3860
i'd really love to integrate this in at some point to dagger (shouldn't be too tricky actually, though the cloud integration might be harder), but one of the bigger blockers here is that we're looking at switching to the containerd worker soon in the future. currently, resource usage monitoring is only supported for the oci/runc worker.
the generalized problem of working out how to estimate cpu/memory is really hard though, it's very much a manual process.
generally the right call is to use the pressure information https://www.kernel.org/doc/html/latest/accounting/psi.html exposed by the kernel, which gives you some idea of what resource a process was blocked on - then you can adjust from there.
oblique vortex
in addion to that, I recall helping some folks integrating cadvisor (https://github.com/google/cadvisor) with Dagger so they had more visibility about the underlying containers were effectively doing. Even though it's a bit more work, you could set this up as well to get a baseline performance of your steps
tawdry maple
got it! thanks for the pointers
hmmm something tells me cadvisor won't run on mac with https://orbstack.dev/
