![]() Firstly, developers now have the option of using a new experimental file sharing implementation called virtiofs (the current default is gRPC-FUSE). I'm not really sure where to go from here. The 4.6 release of Docker Desktop for Mac contains a number of changes that drastically improve file sharing performance for macOS users. I'm using Docker's -v host/folder:container:/folder to mount the codebase into the container. It is important to identify if this is a requirement for your container. However, if the container utilizes Persistent Docker Volumes, disk usage is likely to go up. A container with a running image takes up 150-700 MB of disk space on average. The host outputted in bytes and the container in mbs, but converting those numbers, the speed difference is about 10 times the speed. On Docker for Mac, everything works the same, but the performance is awful. This is because there’s usually a cap on the storage that Docker containers can occupy on the disk. I tested the disk speed with dd and the results within the container: $ time sh -c "dd if=/dev/zero of=ddfile bs=8k count=25000 & sync" rm ddfileĢ04800000 bytes (205 MB) copied, 4.23099 s, 48.4 MB/sĪnd on the host: $ time sh -c "dd if=/dev/zero of=ddfile bs=8k count=25000 & sync" rm ddfileĢ04800000 bytes transferred in 0.482290 secs (424640750 bytes/sec) ![]() I used this script initially because I was debugging a web app but it seems it's the disk read itself. I'm using Boot2Docker, so i'm actually now wondering if the issue is vboxsf? I have some extremely slow disk IO within a Docker container.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |