3 ms·
Have you done any stress testing yet? I've run into some contention problems with more than a couple hundred containers per node. I imagine most other deploymen
by dvanduzer 12y ago
Have you done any stress testing yet? I've run into some contention problems with more than a couple hundred containers per node. I imagine most other deployments haven't required that kind of density so far...
- robszumski 12y agoWhat types of issues are you seeing? From time to time it's easy to get hundreds (or thousands) of containers on a machine. I know docker is a bit slow to start up with a lot of containers, but because of the socket activation that shouldn't be an issue at all if you're starting containers via systemd or fleet.
- dvanduzer 12y agoI gave Blake the whole rundown (i.e. laundry list of whines) at GopherCon, and it sounds like a lot of the issues I ran into are fixed in more recent images. I was attempting to inject 1000 containers running a small node.js app into 3 168GB AWS instances via fleet 0.1.3 (I think). Part of my problem may have been that I was sharing some config data between app instances via Redis, when I could've just used etcd for that.
- marceldegraaf 12y agoNope, I haven't. I'm just getting started with all this, so I've got a lot to explore and learn... :-)