-
Notifications
You must be signed in to change notification settings - Fork 508
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
Possible Containerd Startup Latency Increase #4163
Comments
Not sure if this is helpful, but this is the same command when evaluating Bottlerocket a couple years ago. It's pretty old, but at least shows some precedence for faster boot up times.
|
This seems like a significant outlier for an
There may be some combination of CPU or I/O throttling at play in the 29 second case. Some data points for a t3.small launch in EC2:
The recent addition of the SOCI snapshotter dependency definitely delays the |
Image I'm using:
aws-dev
variant using core kit v2.3.5. Built using the following commands:What I expected to happen:
I expect containerd to start up in ~1.5s after running
/bin/systemctl try-restart containerd.service
.What actually happened:
It takes roughly ~6s for containerd to start.
How to reproduce the problem:
systemd-analyze blame
The text was updated successfully, but these errors were encountered: