-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Add a limit in the graph code for number of metrics #6100
Conversation
This avoids running each metric name through several function calls by doing the fuzzy filtering earlier. It also moves the history construction into the function rather than multiple places. Signed-off-by: David Leadbeater <[email protected]>
Browsers start to get slow if this element has more than around 5,000 items in it. Signed-off-by: David Leadbeater <[email protected]>
Signed-off-by: David Leadbeater <[email protected]>
Signed-off-by: David Leadbeater <[email protected]>
Signed-off-by: David Leadbeater <[email protected]>
This imports the changes from the currently unmerged pull request at prometheus/prometheus#6100. Signed-off-by: David Leadbeater <[email protected]>
This imports the changes from the currently unmerged pull request at prometheus/prometheus#6100. Signed-off-by: David Leadbeater <[email protected]>
Signed-off-by: David Leadbeater <[email protected]>
Any updates on this? On the Thanos side, this kind of code makes sense where we easily have terabytes of data and solves the original problem mentioned here but I also think it's understandable if on the Prometheus' side you don't want to have such logic embedded in the UI's code. |
@juliusv is this still relevant? |
Closing, would need updating for the new UI anyway (which mostly seems faster, although the fuzzy matching still seems expensive). |
Plus a few optimisations, this improves the situation for #5919.