Based on the documentation here, https://nginx.org/en/docs/ngx_core_module.html#worker_processes
The worker_processes is defined as the number of worker processes.
The optimal value depends on many factors including (but not limited to) the number of CPU cores, the number of hard disk drives that store data, and load pattern. When one is in doubt, setting it to the number of available CPU cores would be a good start (the value “auto” will try to autodetect it).
Most of the guides recommend setting this value to the number of cores on the server or set to auto which itself sets it to the number of cores on the machine.
I'm running OpenResty on kubernetes so when I check the number of CPU cores from inside the openresty pod, it returns me the number of cores my physical machine (node) has. However, with CPU requests & limits on the k8s, all the 8 cores wouldn't be available for the pod.
So what should be worker_processes's value for shared CPUs in case of kubernetes?
On 7 May 2021, at 15:02, Kshitij Joshi <kshiti...@gmail.com> wrote:
You received this message because you are subscribed to the Google Groups "openresty-en" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openresty-en...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openresty-en/203711dc-1163-4c32-8e60-f3999bd2d388n%40googlegroups.com.
On 7 May 2021, at 16:11, 'ecc256' via openresty-en <openre...@googlegroups.com> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/openresty-en/bac4c471-e891-4f8c-bbb7-cbf5975399e9n%40googlegroups.com.
On 7 May 2021, at 16:47, Kshitij Joshi <kshiti...@gmail.com> wrote:
Thanks a lot Igor!
To view this discussion on the web visit https://groups.google.com/d/msgid/openresty-en/fa272561-4854-4063-8baa-863934030083n%40googlegroups.com.