[Pdns-users] rec_control with forking

[Nico van Royen]

Using rec_control we're trying to get some accurate data on how much the pdns-recursor can take on varrious hardware setups.  We are however running into some hickups when running the recursor with the "fork=yes" options.

When the recursor is forked, there seems so way that the rec_control can utilize the socket since it basicly has 2 different processes (thus also 2 pid's) and 2 different socket files with its pid attached.  Any stats made now (when running with no forking) are picked up by rrdtool to give us some insight in what pdns can manage. (we're attempting to stress out the server using the queryperf tool from bind9).

Running it from several sources to a single instance if the recursor gives us an average of 8500 qps at 99% (single-)cpu usage on low-specs hardware.   We might asume this will increase by (guessed) 75% when running it forked (since its a dual cpu setup) but accurate stats would be nice.  Question is ... how to get those stats if rec_control can't give it ?

Also..  is it safe to asume that:
pdns recursor (when stressed) likes: big cpu + big mem (for caching) ?
pdns authorative (using gmysql from external sql server): likes: big cpu + low/medium memory ?

Thanks,
Nico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20061011/e75661d9/attachment.html>