About LXD container density and best practices for overcommit

LXD
4

I cannot think of a reference on this, of someone that went through the process and documented the workload for their real production environment.

If you would like to go ahead, set out the workload and then see how it performs, you can

  1. run lxc info mycontainer1 for each container to get the current and peak memory use. See How to monitor LXC running container metrices during migration phase as well.
  2. use sysdig (see: https://blog.simos.info/how-to-use-sysdig-and-falco-with-lxd-containers/ ) in order to get more direct information through the lifetime of the containers. Note that sysdig installs a kernel module that collects all sorts of information. There are tutorials on how to set up the checking of memory requirements for containers, such as https://sysdig.com/blog/monitoring-greedy-containers-part-1/
1 Like