3 ms·
Docker performance impact might as well be zero. You're actually using the system kernel, with the application's filesystem (thus dependencies) and other resour
by dotancohen 5y ago
Docker performance impact might as well be zero. You're actually using the system kernel, with the application's filesystem (thus dependencies) and other resources (CPU, memory, network access) namespaced away from the rest of the system. So there is no e.g. mapping on top of the extant kernel mapping. I've not noticed and performance impact, though obviously my workflow isn't your workflow.
Seriously, try it. I personally use docker-compose, even for single containers.
- pornel 5y agoDocker is reasonably performant only on Linux. On macOS it's a fat slow VM that bogs down the whole machine (unless you make the VM even slower by giving it fewer CPU cores), has a horrendously slow network file system, and it's managed by a needy Electron app. And don't forget that all new Macs are now ARM-based, so x86-based Docker images don't work. My gripe with C is that everyone pretends it's portable, but only care about porting to one (their) platform. It's easy: just use pkg-config/docker/nix. Windows? macOS? Who cares!? Just run a Linux VM!
- duped 5y ago> Docker performance impact might as well be zero. But god help you if you care about MacOS and Windows