-
Notifications
You must be signed in to change notification settings - Fork 8
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
Docker for mac performance tuning #61
Comments
Ref: docker/for-mac#6590 |
Devcontainers info: |
Ref: docker/roadmap#7 |
Another test with:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
We all know that Docker performance on mac for some cases is quite limited in terms of filesystem performance, mainly caused by the shared network disk between the host and the docker for mac VM.
There is a long-standing issue you can find here: docker/roadmap#7
We as a company invested a lot in the past to reach close-native performance between Linux and macOS, in the docker-machine era we used NFS sharing which leads to very close native performance, then we decided to mainly use Linux for our developer workstations also to avoid this kind of performance issues.
With the Apple Silicon era, we decided to invest again in macOS for our developer workstations, as the machines are powerful, cheap and with the best-in-class hardware you can find on the market now.
The current Docker for Mac improved a lot the filesystem sharing issues, but it still falls behind the native performance, especially with heavy fs scenarios usage like
Node
andPHP
withnode_modules
andvendor
directories which can become very very big also in simple projects.Benchmark
Repository: https://github.com/paolomainardi/docker-for-mac-bench
I am going to use
create-react-app
as a use case scenario, the test is executed:node_modules
Filesystem
Native
Doker for mac - gRPC Fuse (default)
Docker for mac - Virtiofs (beta)
CPU
macOS 13
The text was updated successfully, but these errors were encountered: