nagios and memory utilization

[Sergey V. Artjushkin]

Hello

Colleagues,
I have small question about Nagios 1.0.
Two days ago, I have replaced old Netsaint 0.6 monitoring tool with new Nagios 1.0 tool.
At this moment, I have about 3000 services to monitor. Most of services is checked
by my perl plugin. 
Nagios is compiled with --with-perlcache,--enable-embedded-perl options and
with Mysql support.
Everything is working well, but I have noticed that sometime Nagios uses to many memory.
It's seems like every time when Nagios have some service sheduled for checking,
it forks new child process.

# top 
PID USERNAME PRI NICE  SIZE    RES STATE  C   TIME   WCPU    CPU COMMAND
 3718    231    64   0   165M 63992K CPU0   1 244:58 15.23% 15.23% nagios
10440 nagios    63   0   585M   207M RUN    0 280:36 13.18% 13.18% mysqld
74528    231    -6   0   165M 66324K pipewr 1   0:00  6.30%  0.88% nagios
74566    231    -6   0   165M 66340K pipewr 1   0:00  8.71%  0.83% nagios
74500    231    -6   0   165M 66328K pipewr 1   0:00  3.31%  0.73% nagios
74516    231    -6   0   165M 66356K pipewr 1   0:00  4.04%  0.73% nagios
74525    231    -6   0   165M 66344K pipewr 0   0:00  3.77%  0.68% nagios
74547    231    -6   0   165M 66324K pipewr 0   0:00  4.90%  0.68% nagios
....

The parent Nagios process (PID 3718) use 165MB  of memory, and each child
process use the same amount of memory. For example when 10 child process is running
they use 1,6GB of memory!!  I think it is too many. 
So my question is, how I can reduce the size of memory that Nagios used??

Thank you for advance.

-- 
With best regards.


-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null