Hi Adam,
With 50 threads it almost makes the 5 minutes for 1 cycle. And a low load of 45. The iotop shows 6 rrdcached procs who are active. I should try to run 100 threads to see what the i/o impact is.
I have a different question. In the menu under ports if see alerts with 14000 alerts. Will the alert go away by them self or is there an option to clear them?
And a second question regarding the fdb-table. If I disable this in the config.php the web page still remains and so does the data in the mysql. Is there a way to delete this data? Or will this go away by itself?
Regards,
Frederik
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: donderdag 10 oktober 2013 15:48 To: Observium Network Observation System Subject: Re: [Observium] poller performance
On 2013-10-10 14:40, F.Reenders@utwente.nl wrote:
I disabled it now. Last time I disabled this I noticed the biggest bottleneck was the port module. That takes about 85% of the total time.
That's because ports accounts for 85% of total I/O :)
You can see how much I/O is being caused by running iostat or iotop. You are almost certainly running far more poller processes than your I/O system can sustain.
the fdb-table module is a lot of SNMP due to Cisco being lazy and not implementing a sensible place to get mac address tables from.
You are definitely running too many threads.
adam. _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium