4 ms·
Benchmarking in Docker in general is a mistake I believe.
by MiroF 6y ago
Benchmarking in Docker in general is a mistake I believe.
- nitrogen 6y agoYou should probably be measuring your app's performance in a production-like environment though.
- ashtonkem 6y agoYou should load test in a realistic environment. Comparative benchmarks should be done in a consistent environment.
- andygrove 6y agoI think it makes sense for software that is intended to run in Docker and frameworks like Kubernetes that use Docker.
- mschuster91 6y agoWhy? The only overhead you have in Docker is on syscalls (due to permission checks, namespaces, ...), everything else runs at 100% native speed - unlike assisted virtualization (at least IOMMU overhead plus overhead for anything involving the filesystem) or emulated virtualization (obvious overheads here).
- edwintorok 6y agoIf both sides of the comparison run inside Docker that is still a valid comparison. With Docker the benchmark should be a bit more reproducible by anyone.
- MiroF 6y agoThere are serious and undocumented problems in Docker. For instance, I spent multiple days investigating an issue in my tests that eventually I realized was due to accessing memory returned by an `mmap` syscall on a Docker mounted FS causing a SIGBUS, but only some of the time. That is super dangerous and shook my confidence in Docker.