-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
slow start-up when not at AWS Seattle offices (I am in Europe) #421
Comments
We originally did not do parallel image pulls because docker was the engine underlying the pulls, and we did not trust it to do them correctly. But we don't have that constraint now. I'm not sure if it's the only thing to blame here, but we can look into that as a start. |
Here is perhaps a slightly more informative trace log output;
Generally, it seems that |
Hi! As mentioned during the community meeting, it takes me somewhere around 15-30 seconds before I get to the build stage. This is at a high level what happens:
Combined Application and Network Timeline
strace -t -f -e trace=network twoliter build variant metal-dev
I had this strace output analysed by an AI and produced this log - but this was of a broken run as you can see by the fact that Cargo.toml was not parse:able.
Perhaps we could at least do all of the images in parallel?
The text was updated successfully, but these errors were encountered: