4 ms·
The question is, why docker have that overhead. Virtualizing should not be very resource-intensive nowadays, everything is optimized at CPU level.
by vbezhenar 6y ago
The question is, why docker have that overhead. Virtualizing should not be very resource-intensive nowadays, everything is optimized at CPU level.
- soraminazuki 6y agoIt's not that simple as "everything is optimized at CPU level," actually. Virtualization has very different performance impacts on different workloads.
- andrewguy9 6y agoVirtualization has pretty high overhead. But on the Mac you have to pay the virtualization overhead to run Linux in a VM, then compound the docker overhead on top of that. On MacBook Pro this is problematic because it eats battery and contributes to thermal problems.
- andrewguy9 6y agoForgot to mention that disk performance on docker on the Mac is a big deal for building software. This article shows overhead for a disk heavy workload: https://vivait.co.uk/labs/docker-for-mac-performance-using-nfs https://vivait.co.uk/labs/docker-for-mac-performance-using-n... He gets 7 second load time natively, but a 56 second load on docker with inconsistent drive link.