One we see a lot is this: https://trac.nginx.org/nginx/ticket/1151 https://trac.nginx.org/nginx/ticket/1151 worker_processes auto; in a kubernetes environ

One we see a lot is this: https://trac.nginx.org/nginx/ticket/1151 https://trac.nginx.org/nginx/ticket/1151 worker_processes auto; in a kubernetes environment where the nginx container only has 1 cpu share, but is running on a 64 core node...this does the wrong thing and launches dozens of workers, which do nothing but eat memory. According to the bug above they've not fixed it because they can't tell the difference between this case and other cases where your cpus may be restricted. While that's true, other systems don't just ignore the problem: http://mail.openjdk.java.net/pipermail/hotspot-dev/2019-January/036120.html http://mail.openjdk.java.net/pipermail/hotspot-dev/2019-Janu... (we also commonly see issues with buffering, and proxy host header not being set; the latter is an issue when code moves from an environment with physical hosts - which don't care about the host header - to virtual ones)