#Slow initialize times with TS Dagger Function
1 messages · Page 1 of 1 (latest)
I'm not doing anything fancy, even the simple echo example takes 1m+ at the intiialize step, before it gets to my code (?)
When I was watching the dagger engine logs, it looked like it might have been churning on layers / cache internally. But the logs are very different from the pre-function days, so I'm not certain
@pliant jolt i am also facing similar thing. Just tried with simple helloe world but it tooks over then 2 min to get the result
Did you able to figure out
No, what appears to be happening for me is that the building of the TS function is what is taking a long time and not caching. If you look at the logs, this is what it seems to indicate to me, and also that my code has not started processing. You'll see logs that indicate your function implementation after a while
Is this only related TS modules? I am not GO person but did you have any chance to tried with go for comparison>
I was about to, now that I literally just worked through a bug in another project :]
Does it mean we should not even start with Typescript to develop modules?
if I ask engineering teams to try and call modules, and if takes more than 2min - it might be dissapointment :/
I'm going to try all 3 SDK starter / hello worlds and post the stats from my mac
I expect this to be something that gets fixed, I can only consider this a bug
I believe so
I might try with an older engine as well, see if it broke with 0.11.0
Would you mind me to ping as well? i will also try to test btw
I'm working on it now, just created the three packages
FWIW, I still use the dagger run setup and it works as expected (not slow)
I actually prefer this DX because I tend to craft a CLI for my devs that is custom to the project
which is inline with what @fierce fractal said in his KubeCon keynote :]