-
Notifications
You must be signed in to change notification settings - Fork 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
Cache LabelValues #39
Comments
Is that actually true? As far as I can tell from code, this only hits all blocks' index files which are already preloaded on store node, right? If that's so, we can close this issue. (: |
Yes, but we are still considering not caching those full files right? My thinking was even with, we could be talking about tens of thousands of blocks at some point. And that might still get expensive then. But you are generally right, this issue was probably opened as a pre-mature concern. |
Ah, sorry, you're right. We will soon move out from this preload-all-index-files heaven. |
Mh, I'll close this for now. On store nodes that data is served entirely from memory now anyway. The full fanout is probably not an issue anymore with that. |
We are exploring loading blocks on demand, so it's time to reopen this as values would be no longer in memory. (: Worth to note that mostly The alternative would be implementing the time limit on this. Also related to the: prometheus/prometheus#6178 |
yup, fixed! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
…ft-4.7-thanos Updating thanos builder & base images to be consistent with ART
Merge latest upstream (3327c5) and update to latest promql-engine (10d1c54)
…nent-version-2.7 Updated component version to 2.7.0
We should keep an eye on the
LabelValues
RPC to store nodes. It will always hit every single block, which can get particularly costly on GCS store nodes.This data does rarely change and is only used for things like auto-completion. But for that it is called whenever the query UI opens up. Probably the query nodes themselves should already cache them.
The text was updated successfully, but these errors were encountered: