Poller from php in ca. 60 sec. to Spine in ca. 298sec.

[morgentau]

I decided to change the poller from PHP to Spine... out of interest and couriosity...

after the change;
12/02/2011 12:55:00 PM - SYSTEM STATS: Time:298.5597 Method:spine Processes:10 Threads:10 Hosts:67 HostsPerProcess:7 DataSources:4310 RRDsProcessed:0
12/02/2011 12:55:00 PM - POLLER: Poller[0] Maximum runtime of 298 seconds exceeded. Exiting.
12/02/2011 12:50:00 PM - SYSTEM STATS: Time:298.1894 Method:spine Processes:10 Threads:10 Hosts:67 HostsPerProcess:7 DataSources:4310 RRDsProcessed:0
12/02/2011 12:50:00 PM - POLLER: Poller[0] Maximum runtime of 298 seconds exceeded. Exiting.

before the change;
12/02/2011 12:36:10 PM - SYSTEM STATS: Time:68.6406 Method:cmd.php Processes:10 Threads:N/A Hosts:67 HostsPerProcess:7 DataSources:4310 RRDsProcessed:1196

What could be the reason for this performance degradation? I thought it should be faster... No?

[gandalf]

This is which version of spine? Self-compiled?
From the data shown, I currently can see, that the number of processes is too high for that few hosts. I'd go with 2 .. 4 as a start
R.

[morgentau]

This is which version of spine? Self-compiled?
From the data shown, I currently can see, that the number of processes is too high for that few hosts. I'd go with 2 .. 4 as a start
R.

This is fresh off the Suse 11.4 installation. Version is 8.7.h... I'll try it with reduced processes...

[morgentau]

This is which version of spine? Self-compiled?
From the data shown, I currently can see, that the number of processes is too high for that few hosts. I'd go with 2 .. 4 as a start
R.

This is fresh off the Suse 11.4 installation. Version is 8.7.h... I'll try it with reduced processes...

----edit

So i changed the parameters but the result is no better. It takes almost 300 sec. and 0 RRD's are processed... i just thougt i will try the spine poller because im adding new ressources and wanted to be prepared for when i reach the 300 sec. limit with the php poller.

12/05/2011 10:40:00 AM - SYSTEM STATS: Time:298.5055 Method:spine Processes:2 Threads:5 Hosts:67 HostsPerProcess:34 DataSources:4326 RRDsProcessed:0
12/05/2011 10:40:00 AM - POLLER: Poller[0] Maximum runtime of 298 seconds exceeded. Exiting.

[phalek]

I'dd suggest playing around with spine first without trying to alter any rrd files. You can do this with e.g. the following command ( as the Cactiuser which the poller usually runs under):

Code: Select all

/path/to/bin/spine -R -C /path/to/etc/spine.conf -O max_threads:5 -O php_servers:2 -O script_timeout:25 -O max_get_size:10 -O concurrent_
processes:1 -V 5 -S >/tmp/spine_testrun_step1.log

You can then check the log file for any potential issues ( e.g. why it's taking longer than the cmd.php mode ) and also checkout different settings without interferring with the normal polling process all the time.