[INFO] PERFORMANCE: Spine 0.8.7a vs cmd.php

[computer_guru]

*****CMD.PHP"*****

Before we started using the spine poller the CPU on our server was over 80+% all of the time. This was because we have the

poller set for every minute and it was taking over one minute for the poller to poll everything. Therefore the poller was running

100% of the time. This was with about 70 hosts. So we had to switch to spine. See below.

*****Spine******

After switching to spine this is how fast everyting started working:

Time:12.3611 Method:spine Processes:20 Threads:30 Hosts:106 HostsPerProcess:6 DataSources:204 RRDsProcessed:121


***** Conclusion *****

We went from over one minute per cycle to under 15 seconds and with more devices being polled!!!


System Specs:

- Ubuntu Dapper Drake 6.06 Server Install
- 2.8 GHz Intel Xeon
- 4 GB Memory

Maximum Concurrent Poller Processes: 20
Maximum Threads per Process: 30
Number of PHP Script Servers: 5

[gandalf]

Maximum Concurrent Poller Processes: 20
Maximum Threads per Process: 30
Number of PHP Script Servers: 5

Please find a related thread in the Announcement forum.
Processes=20 is insane for a single XEON. Use 1-2 times number of CPU cores.
Threads=30 is huge, not necessarily insane. Usually recommended setting is 10-15
Script Servers=5 is required only if using lots of PHP Script Server Scripts. But there should be no overhead specifying this number.
Use latest rrdtool on linux to increase speed by another 30% or the like. And latest spine will be better as well.
Reinhard

[staind420]

clowned him