Improve performance of Cacti poller on heavily loaded systems #4414
Description
Feature Request
Is your feature request related to a problem? Please describe
On heavily loaded databases, where there is little I/O capacity available, updates to the poller_item table can block the Cacti poller. In those cases, where there is only one Data Source Profile active, you can reduce the I/O load and therefore unblock the poller by simply not performing the updates to the rrd_next_step variable.
Describe the solution you'd like
Cut almost 50% of the polling time for large system with many data sources and very active databases.
Describe alternatives you've considered
Lot's and nothing so far has worked. This has.