-
-
Notifications
You must be signed in to change notification settings - Fork 405
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 table performance by caching 'Total Rows' using a hash #4989
Labels
Milestone
Comments
TheWitness
changed the title
Cacti 'Total Rows' by Hash to Improve Performance
Cache Cacti 'Total Rows' by Hash to Improve Performance
Nov 6, 2022
TheWitness
added a commit
that referenced
this issue
Nov 6, 2022
Cache Cacti 'Total Rows' by Hash to Improve Performance
TheWitness
added a commit
that referenced
this issue
Nov 7, 2022
* When performing maintenance, remove old rows from the row cache * When removing a user, make sure you remove their old data.
TheWitness
added a commit
that referenced
this issue
Nov 7, 2022
* If you are calling "is_device_allowed()" don't cache the row counter * Switch from $host_id to $device_id
Outstanding issues:
|
TheWitness
added a commit
that referenced
this issue
Nov 7, 2022
* Don't cache on is_graph_template_allowed() calls.
Covered |
Still making some changes here. |
TheWitness
added a commit
that referenced
this issue
Nov 20, 2022
netniV
changed the title
Cache Cacti 'Total Rows' by Hash to Improve Performance
Improve table performance by caching 'Total Rows' using a hash
Dec 31, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature Request
Is your feature request related to a problem? Please describe
On large systems where there can be millions of rows, it's important not to have to continually calculate the number of total rows as this will slow down the Graphical User Environment.
Describe the solution you'd like
Instead, cache these values until the number of objects for the particular cache item changes. This is specifically important for objects like:
Additional context
We should build the API, and then implement in the permission functions, and then publish the API for plugin developers.
The text was updated successfully, but these errors were encountered: