Re: net::server::prefork fork too much (config)

My first guess is just that you configured things badly. You don't include any information about how you configured things, so I'm left to guess. But, for example, if you set max_spare_servers to 0 and min_servers to 2, then you force it to repeatedly kill the two extra idle children and repeatedly add children to get back to the minimum of 2.

Yes, you could patch the module to try to prevent this misbehavior when a user of the module misconfigures it.

- tye

Comment on Re: net::server::prefork fork too much (config)

Replies are listed 'Best First'.
Re^2: net::server::prefork fork too much (config) by psini (Deacon) on May 11, 2008 at 07:03 UTC
sorry, you're right, I forgot to post the config file. .This is the relevant portion: `log_level 4 log_file Sys::Syslog syslog_logsock unix syslog_ident tmp syslog_logopt pid syslog_facility local1 pid_file /var/run/tmp.pid serialize flock min_servers 5 min_spare_servers 3 max_spare_servers 10 max_servers 30 max_request 100 child_communication 1 port 9999 host * proto tcp listen SOMAXCONN user www-data group www-data background 1 setsid 1` [download]	[reply] [d/l]
Re^3: net::server::prefork fork too much (config) by tye (Sage) on May 12, 2008 at 14:44 UTC
I'd try setting min_servers and min_spare_servers to be equal. If that stops the thrash, then you should submit a patch for the module that improves its logic to prevent this problem. - tye	[reply]