next up I'm also gonna get to the bottom

[regal shuttle]

running both of them together against a local dev engine uses maybe like 8GB max and 100% of my cpus, I have never head my m4's fans get this loud... so I could definitely see those two getting co-scheduled on the same instance being an issue potentially

i'll see if there's some obvious reason it's so performance intensive (maybe the need for qemu emulation?) and if there's anything we can do

@sterile zephyr your PR just hit this: https://dagger.cloud/dagger/checks/github.com/dagger/dagger@fbd5cf31e130841f358b85373f6534909451eb6d?check=cli:release-dry-run

I'm gonna do some re-runs to see if I can trigger it again and watch the namespace instances live 🍿

I wouldn't block your PR on those though

[sterile zephyr]

feel free to merge when you want 🙏

[regal shuttle]

Yeah, this is what is looks like on the namespace instance

go build/link is taking more RSS than the engine even 🧐

And CPU is obviously very red and angry

[regal shuttle]

merged

As part of theseus there are some specific areas where we actually have more parallelism than previously... possible that is actually hurting us here

or maybe something else changed here, not sure yet