Closed bparees closed 5 years ago
I just did a buildah pull of this image locally and time shows.
real 0m52.165s user 0m30.642s sys 0m5.124s
Docker took real 0m45.643s user 0m0.188s sys 0m0.147s
ALthough I am not sure I compared apples to apples.
@mtrmac Any ideas?
Not at all; vaguely guessing about something I don’t understand: cloud CPU/IO throttling?
How many IOps does buildah do vs docker in your local tests? On a local disk / SSD you might not notice the difference between the two if one does a substantially higher number of IO operations (smaller writes) but on a cloud you're going to be heavily punished if you do.
(i.e. if we're not using buffered writers to disk in buildah you would see this much more)
@nalind PTAL
@vrothberg me thinks that a by product of your #1244 is addressing this issue too. Could you verify please?
I don‘t think so; the logs shows processing in storageImageDestination.Commit
after all the copies and possible caching has happened; it is extracting on-disk tar files to on-disk image storage.
@sjug is looking into iops comparison with docker.
Built buildah master (non-parallel) and compared it to docker disk usage. (Google Doc)
Very unusual findings as the write speed is quite high for docker but the IOPS are very low, perhaps the io write size is larger for docker?
edit: This was on EC2 gp2 disks
@nalind @mtrmac WDYT?
@bparees @nalind @mtrmac Any progress on this?
i haven't touched it but @mffiedler recently opened a bug about slow build performance in 4.x, it would be nice to know if this is part of that and whether it can be improved in the 4.0 timeframe.
Well we did put a bunch of improvements into buildah 1.7 which is not vendored into OpenShift yet. But we are working on other improvements as well. We should be able to get these into 4.X
Well we did put a bunch of improvements into buildah 1.7 which is not vendored into OpenShift yet.
Any reason for us not to go ahead and pull buildah 1.7 in now?
/cc @nalind @adambkaplan
Nope, I would advise it, but I do not know the procedure.
Nope, I would advise it, but I do not know the procedure.
sounds good, we'll take care of it.
Closing this issue.
i'm seeing 8 minutes to extract layers for an image:
There is nothing special about the image that i know of, the image in question is
docker.io/centos/ruby-22-centos7
you can see the full buildah logs here: https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/21556/pull-ci-openshift-origin-master-e2e-gcp-builds/200
/cc @smarterclayton