-
Notifications
You must be signed in to change notification settings - Fork 785
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
buildah images
very slow
#3369
Comments
@vrothberg PTAL |
For reference, here is the actual output of |
Thanks for reaching out. Starting with v1.21.0, Buildah uses a new backend for managing images which is much faster. Can you run |
Side by side:
It is indeed substantially fast-er, but overall still quite a bit slower than preferable. Is it going through image contents in order to compute this metadata listing? |
The weird thing is that this behavior isn't consistent: sometimes, after messed around with buildah enough (not sure what specifically--a couple of
As if there's a cache that needs to get warmed up... |
Thanks for providing the data, @kwshi!
Yes, mostly for computing the size of an image. The remainder should be fast.
Your observation aligns with the ones made in containers/podman#6288. However, we never managed to get a reliable reproducer to figure out why image listing is suddenly slow. Ultimately, it seems more like an I/O performance issue outside of Buildah/Podman. |
That being said: unless we know what causes the I/O degradation, I do not know what to do. A reliable reproducer would be ideal. |
Update: I still don't have a reliable reproducer for the bad IO, but I've noticed that one seemingly reliable way to suddenly speed image listing up is to |
@rhatdan, could you talk with Vivek about this issue? There seems to be a pattern but we couldn't pin it down yet. |
@rhvgoyal WDYT? |
I am assuming you are using "stat()/fstat()" to get to file size. So that should not slow down significantly because of file size. There is a small possibility that cloud provider is doing some I/O throttling. I mean what else is going on host? If you have done lot of I/O already and have run out of credits, then cloud provider might throttle and delay I/O. Or it is possible that this command is waiting for some lock and that lock is held by other path which is doing I/O and that has been throttled. So effectively a simple action of listing images is blocked. I think one needs to patch buildah/podman code and see what are we waiting on and first narrow it down a bit. |
I'll add that, in my own situation at least, the container is store is simply located on a separate local partition on an SSD, so the cloud-provider-throttling behavior shouldn't be a factor. |
I do not know what constitutes as slow today but I consistently get ~7s for 50 images (and ~12s in usr respectively). Using |
@septatrix, which version of Buildah are you running? |
@edsantiago, FYI. Maybe something to look out for. If you ever find something that may contribute to a slow(er) storage access, feel free to drop it here. |
One thing I notice is that Buildah is surprisingly faster(sometimes half the time) than Podman (reproducer |
I should have been more precise. My timings are for podman and not for buildah. (And I am using podman 3.2.3) |
A friendly reminder that this issue had no activity for 30 days. |
@kwshi We believe this issue is solved, reopen if I am mistaken. |
I don't believe this is fixed. See my previous comment (#3369 (comment)): there's still things we need to investigate. |
I agree that this is not yet fixed; I just downloaded the latest release (v1.22.3) and am still having the same problem. I am still working on finding a reliable reproducer/pinning down the exact cause of the slowness. |
I found the cause (Podman issue containers/podman#11997) and am working on a fix. |
Here is a fix: containers/common#811 |
Closing, will be implicitly fixed with the next vendor of c/common. |
Description
My containers store has a lot of large images, totaling ~40-50 tagged images & ~1TB size. For some reason, this causes
buildah images
(as well aspodman image ls
) to run very slowly:I'm not sure what the exact cause is, but I think it is abnormal/unusual for performance of merely listing images to deteriorate at sizes as small as ~50 images and ~1TB. Perhaps I'm doing something wrong?
Steps to reproduce the issue:
time buildah images
ortime podman image ls
Describe the results you received:
Listing images takes ~2minutes.
(Perhaps relatedly,
podman system df
is also kind of slow, but much less so--only takes about 15s.)Describe the results you expected:
Listing images should happen approximately instantly.
Output of
rpm -q buildah
orapt list buildah
xbps-query buildah
:Output of
buildah version
:Output of
podman version
if reporting apodman build
issue:Output of
cat /etc/*release
:Output of
uname -a
:Output of
no conf, using defaults--here'scat /etc/containers/storage.conf
buildah info
:The text was updated successfully, but these errors were encountered: