Contribute to Docker to decrease it's startup/teardown time

[treeder]

See: “The Overhead of Docker Run” @treeder https://medium.com/travis-on-docker/the-overhead-of-docker-run-f2f06d47c9f3

[nikhilm]

I believe @rdallman has some numbers on overlay vs btrfs (the latter being
really slow).

On Wed, Oct 12, 2016 at 6:09 PM, Travis Reeder notifications@github.com
wrote:

See: “The Overhead of Docker Run” @treeder https://github.com/treeder
https://medium.com/travis-on-docker/the-overhead-of-docker-
run-f2f06d47c9f3

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#156, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEzWsBH5e4WRnNSS8-3JnmWLC3s7PM0ks5qzYS4gaJpZM4KVYWN
.

[rdallman]

check it out, btrfs (left) vs overlay2 on our default cluster, each data point is the mean of 1 hour (ran for few hours):

[rdallman]

damn those images suck... redoing:

[rdallman]

stop container isn't a good data point really, the process inside can take a while, but there's still a large disparity due to docker being slow w/ btrfs

[treeder]

Is that really 1.83 minutes?

[rdallman]

Well it ain't Photoshop

On Mon, Oct 17, 2016, 7:55 AM Travis Reeder notifications@github.com
wrote:

Is that really 1.83 minutes?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#156 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACzJR_TgAvSsqIr1ZImdzmrBPl2a3-zBks5q04xSgaJpZM4KVYWN
.

[treeder]

I wonder if Docker has a lock/mutex while doing these operations so only one can run at a time...?