nginx causes cpu burst problem when it is received USR1 signal by logrotate script

[Igor Sysoev]

On Mon, Oct 18, 2010 at 03:54:12AM -0400, hakutoitoi wrote:

> Hi,
> 
> I'm using nginx/0.7.67 on the freebsd-6.4
> $ nginx -V
> nginx version: nginx/0.7.67
> built by gcc 2.95.3 20010315 (release)
> configure arguments: --prefix=/usr/local
> --conf-path=/usr/local/conf/nginx/nginx.conf
> --pid-path=/usr/local/var/run/nginx.pid
> --lock-path=/usr/local/var/run/nginx.lock
> --http-client-body-temp-path=/usr/local/var/run/nginx/client_body_temp
> --http-proxy-temp-path=/usr/local/var/run/nginx/proxy_temp
> --error-log-path=/usr/local/logs/nginx/error
> --http-log-path=/usr/local/logs/nginx/access --with-select_module
> --with-http_perl_module --with-debug --with-http_stub_status_module

> 41673 nginx            1  96    0 27480K  8040K select
> 0  11:27  0.05% nginx

Why do you use the poor select method ? FreeBSD has very good kqueue method.
This CPU burst may be caused by nginx bug in select method handling.


-- 
Igor Sysoev
http://sysoev.ru/en/