3 ms·
> Some container disk I/O is much slower than expected. See docker/for-mac#5389. Disk flushes are particularly slow due to the need to guarantee data is written
by nicoburns 6y ago
> Some container disk I/O is much slower than expected. See docker/for-mac#5389. Disk flushes are particularly slow due to the need to guarantee data is written to stable storage on the host.
Huh. This could be problematic given that Docker disk performance on macOS was already dreadful on intel machines. I would love to see Apple give this some attention.
- pella 6y agoOuch ... ~10x slower ???? https://github.com/docker/for-mac/issues/5389 https://github.com/docker/for-mac/issues/5389 from a github comment: "Such a surprise every time I import a database to see it run about 10x slower than amd64."
- londons_explore 6y agoSince a lot of use of docker on a desktop machine has no requirement for data resiliency (web dev work where all containers can easily be wiped and rebuilt), it would be good to have a flag for "no flush" which just ignores all flush requests.
- hashkb 6y agoYou still want e.g. incremental rebuilds and file watching for tests and all that. It's really sad to hear this hasn't been addressed in years. Development with Compose on Linux is such a pleasure.
- londons_explore 6y agoYou can still have all that - flushing behaviour only affects things if the host machine suddenly kernel panics or loses power. For a laptop with battery backup that's probably a once a year occasion. In that case, I'd be happy to wait a few minutes for some docker stuff to be rebuilt.
- hashkb 6y agoYou can't, when you're on a Mac and your code is bind-mounted into the container. This is the most comfortable method of development for me, and works perfectly on Linux. https://github.com/docker/for-mac/issues/3677 https://github.com/docker/for-mac/issues/3677
- tommoor 6y agoYea, I think this is the same issue: https://news.ycombinator.com/item?id=26332732 https://news.ycombinator.com/item?id=26332732 Still an issue in the latest RC today