Wim,
Thanks for the info, particularly the config file values. It is always
good to see what works for someone on a large network. Are you using the
"sql_dont_try_update" directive? I have been thinking of trying this
to reduce the database bottle neck.
Wim Kerkhoff wrote:
Hey
I'm monitoring 7500+ hosts and pmacct keeps up fine. Biggest bottleneck
is the backend database and pure disk I/O.
Before starting pmacctd, my start script does:
echo 512000 > /proc/sys/net/core/wmem_max
echo 512000 > /proc/sys/net/core/rmem_max
Here are some values from the config file:
plugin_pipe_size: 512000
plugin_buffer_size: 4096
sql_cache_entries: 99991
! eof
Wim
Pajlatek wrote:
Hi
I am monitoring a large area network if anyone has similiar network,i
would be glad to know what vaules are u guys using and if they can be
set via pmaact.conf and /etc/systlc.conf only?
As for release i think some example values would be nice to include in
next version.
Thanx for help
Peter
Error follows:
increase shared memory size, 'plugin_pipe_size'; now: '9966020'.
debian pmacctd[15133]: - increase buffer size, 'plugin_buffer_size';
now: '900'.
debian pmacctd[15133]: - increase system maximum socket size.
_______________________________________________
pmacct-discussion mailing list
[email protected]
http://muffin.area.ba.cnr.it/mailman/listinfo/pmacct-discussion
