2 ms·
I don't think running processes inside a container will be any more interesting for benchmarking than just running the processes normally. What overhead does a
by chrisseaton 9y ago
I don't think running processes inside a container will be any more interesting for benchmarking than just running the processes normally. What overhead does a container add? A little indirection in syscalls? I would imagine the number of instructions involved in that are beyond trivial for serving a page, so I can't see how benchmarking running containers would be different than just benchmarking running your processes.
VMs - now with processor virtualisation technology I'm sure the different processor architectures do make an interesting difference there.
- myrandomcomment 9y agoIn some of our scaling test where each container had an IP connecting out to a remote system we ran in to a ton of issues at scale that we did not see running the same number of processes on the bare metal. The overhead of the namespace can add up.
- nwmcsween 9y agoThis is due to the what the container orchestratior uses to route traffic, check out project calico for low overhead networking.
- myrandomcomment 9y agoThe issue had everything to do with how Linux handles networking when you have 1000 container interfaces on a single system. Tweaking net.ipv4.neigh.default.gc* solved most of the issues. I am familiar with Calico and it would not have solved it.