-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
investigate, refactor preload tar balls #7804
Comments
alternatively we could separate the tarballs for kubernetes core images and aux images and binaries |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
This would improve performance, but before we do minikube/pkg/minikube/machine/cache_images.go Line 139 in 070cbb9
My guess is we're looking at a small performance improvement (<1s), but it should be easy enough to do, especially if we compare preloaded images to images that need to be loaded here:
|
If we end up implementing the idea mentioned here -- #10438 (comment) -- then this issue is obsolete. |
when doing preload PR for containerd I had a couple ideas and question
if user adds images using cache add
if they add one couple images using cache add ( as part of a development workflow)
if they start agian are we invoking a reset on all pull ?
can we refactor to DockerImagesPreloaded to return list of not preloaded images ( instead of bool)
so we only pull and load the images that do not exist as opposed load all images again ?
The text was updated successfully, but these errors were encountered: