3 ms·

That's an awful lot of conjecture. I'd wager that most of what you would actually be running in a container would not have its memory usage significantly affect

by Rapzid 11y ago

That's an awful lot of conjecture. I'd wager that most of what you would actually be running in a container would not have its memory usage significantly affected by the presence or absence of optional shared libs.. I'm with the parent on this; such claims warrant research.

ploxiln 11y ago
Not really, it was an educated guess, and then a description of how binaries and libraries work on modern unix systems. Here's a quick demo based on the trivial example of the memcached docker images I mentioned in another thread: vagrant@dockerdev:/host/scratch/janus-gateway$ sudo docker run --name=mc_big --detach --publish=11212:11211 --user=nobody sylvainlasnier/memcached /usr/bin/memcached -v -m 64 -c 1024 67c0e406245d341450c5da9ef03cbf60a8752433a4ace7471e2a478db9a62e07 vagrant@dockerdev:/host/scratch/janus-gateway$ sudo docker run --name=mc_small --detach --publish=11213:11211 --user=nobody ploxiln/memcached /bin/memcached -v -m 64 -c 1024 11037b69acfbc0de7601831634751cd342a7bafe9a25749285bc2c2803cc1768 vagrant@dockerdev:/host/scratch/janus-gateway$ top c -b -n1 | grep 'COMMAND\|memcached' PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5984 nobody 20 0 316960 1192 768 S 0.0 0.1 0:00.02 /usr/bin/memcached -v -m 64 -c 1024 6091 nobody 20 0 305256 780 412 S 0.0 0.0 0:00.00 /bin/memcached -v -m 64 -c 1024 Notice the significant difference in RES (resident set size) and SHR (shared memory). Less trivial processes will have more shared libraries and bigger differences here. Multiply this kind of result times all the contained processes. It adds up.
- Rapzid 11y ago
  Sorry, I was responding to your post in the context of logician's "an important concern" assertion. You and jabl are correct technically of course. Within the context of "an important concern" though; the difference in RES and SHR between the two is about ~330kb. I suspect most people wouldn't find that significant particularly given memcached's common use cases.

by Rapzid 11y ago

ploxiln 11y ago

Not really, it was an educated guess, and then a description of how binaries and libraries work on modern unix systems. Here's a quick demo based on the trivial example of the memcached docker images I mentioned in another thread: vagrant@dockerdev:/host/scratch/janus-gateway$ sudo docker run --name=mc_big --detach --publish=11212:11211 --user=nobody sylvainlasnier/memcached /usr/bin/memcached -v -m 64 -c 1024 67c0e406245d341450c5da9ef03cbf60a8752433a4ace7471e2a478db9a62e07 vagrant@dockerdev:/host/scratch/janus-gateway$ sudo docker run --name=mc_small --detach --publish=11213:11211 --user=nobody ploxiln/memcached /bin/memcached -v -m 64 -c 1024 11037b69acfbc0de7601831634751cd342a7bafe9a25749285bc2c2803cc1768 vagrant@dockerdev:/host/scratch/janus-gateway$ top c -b -n1 | grep 'COMMAND\|memcached' PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5984 nobody 20 0 316960 1192 768 S 0.0 0.1 0:00.02 /usr/bin/memcached -v -m 64 -c 1024 6091 nobody 20 0 305256 780 412 S 0.0 0.0 0:00.00 /bin/memcached -v -m 64 -c 1024 Notice the significant difference in RES (resident set size) and SHR (shared memory). Less trivial processes will have more shared libraries and bigger differences here. Multiply this kind of result times all the contained processes. It adds up.

Rapzid 11y ago
Sorry, I was responding to your post in the context of logician's "an important concern" assertion. You and jabl are correct technically of course. Within the context of "an important concern" though; the difference in RES and SHR between the two is about ~330kb. I suspect most people wouldn't find that significant particularly given memcached's common use cases.