Slow stdout execution

[tall jewel]

Hi,
I'm trying to understand why retrieving the output of a function call is very slow.
I understand that file copies in and out of container takes time as requiring a full sync, but in this use case, I am just outputting a small json structure, and the stdout call takes 30 sec (half of the full execution time)
I'm wondering what's consuming this time, and if there's a way / workaround to speed it up ?
Here is a trace : https://v3.dagger.cloud/mikael-bc/traces/b42be4c4a607f11f4069744d030a3ba0?listen=8c33f0598ac11f62&listen=4823552840a3b111

Any help appreciated 🙂

[timber zephyr]

this seems odd indeed. cc @stoic sky I'm a bit confused about the HTTPRequest at the end. Have you seen these before?

[stoic sky]

My guess is it's the image fetching, and it's not being properly attributed to container.from

[timber zephyr]

thought about that but since this was running in a local trace I assumed that the image should (?) have been cached.

@tall jewel if you run the same pipeline again but with a slightly change in the dotnot-gitversion with-exec. Does it still take that much time?

[tall jewel]

Annoyingly the stdoout is now quasi instant, whatever I do (clear cache, make change on the container ...) 😅
I'll try that next time it happens

[timber zephyr]

If you delete the Dagger engine container I'd assume it will take quite some time again as it'll have to re-download the image

[tall jewel]

Thinking, it's probably obvious, but if all I need from a function execution is the output inside a container, i'd much better call the stdout() in the function than in the command line right ? That way, the container created in the function doesn't need to be downloaded on the host ?
eg
//in module
return dag.container()(...).stdout()
//in shell
dagger call my_function

rather than
//in module
return dag.container()(...)
//in shell
dagger call my_function stdout