Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve performance of Cacti poller on heavily loaded systems #4414

Closed
TheWitness opened this issue Sep 30, 2021 · 1 comment
Closed

Improve performance of Cacti poller on heavily loaded systems #4414

TheWitness opened this issue Sep 30, 2021 · 1 comment
Labels
enhancement General tag for an enhancement resolved A fixed issue
Milestone

Comments

@TheWitness
Copy link
Member

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.

@TheWitness TheWitness added the enhancement General tag for an enhancement label Sep 30, 2021
@TheWitness TheWitness added this to the 1.2.19 milestone Sep 30, 2021
TheWitness added a commit that referenced this issue Sep 30, 2021
Improve performance of Cacti poller on heavily loaded systems
@TheWitness TheWitness added the resolved A fixed issue label Sep 30, 2021
@TheWitness
Copy link
Member Author

This is resolved. There will be a spine change related to this in the next few minutes as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement General tag for an enhancement resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

1 participant