agent: Add support for simplified LFC scaling #1186
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We have one ongoing issue where the LFC goal size algorithm is hitting degenerate edge-case behavior on a large workload -- but because of that bug, it's hard to tell whether the impacted workload *can* be feasibly autoscaled with the information we have available. For large workloads, it's reasonable enough to just look at the 1-hour working set window, and testing with that will indicate whether we need to look at a longer time horizon to effectively scale LFC on such a workload -- or if the information we already have should be sufficient. See also neondatabase/cloud#22214 for more information.
No changes to the coverage.
HTML Report |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have an ongoing issue where the LFC goal size algorithm is hitting degenerate edge-case behavior on a large workload — but because of that bug, it's hard to tell whether the impacted workload can be feasibly autoscaled with the information we have available.
For large workloads, it's reasonable enough to just look at the 1-hour working set window, and testing with that will indicate whether we need to look at a longer time horizon to effectively scale LFC on such a workload — or if the information we already have should be sufficient.
See also neondatabase/cloud#22214 for more information.