Use of worker_cpu_affinity in hyper-threading context

Server NGINX
1

Hi,

I have one E3-1240 v3 CPU here, which has 4 cores with hyper-threading
enabled. Currently I have the following setup in nginx.conf:

worker_processes 4;
worker_cpu_affinity 10100000 01010000 00001010 00000101;

In other words, I bind each of the four workers to two (virtual) cores
(similar to example in
Core functionality). For
a medium-sized frequented site, would you consider this the “correct”
way? Or would you leave out the worker_cpu_affinity setting and let the
CPU scheduler do the rest?

Thanks for your help.

Alex

2

Hello!

On Thu, Nov 20, 2014 at 07:37:56PM +0100, Alex wrote:

Core functionality). For a
medium-sized frequented site, would you consider this the “correct” way? Or
would you leave out the worker_cpu_affinity setting and let the CPU
scheduler do the rest?

Unless in your workload nginx is CPU-bound, I would recommend to
let the OS scheduler to do the work.

–
Maxim D.
http://nginx.org/

3

Hello Maxim,

On 2014-11-21 20:23, Maxim D. wrote:

Unless in your workload nginx is CPU-bound, I would recommend to
let the OS scheduler to do the work.

Thanks, than I will let the OS scheduler decide (in my workload,
php5-fpm is CPU-bound).

Again, appreciated your help!

Alex