Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upCache labelset->fingerprint lookups #307
Comments
This comment has been minimized.
This comment has been minimized.
|
Not applicable anymore to how we do things in the query layer nowadays. Closing. |
juliusv
closed this
Jul 22, 2015
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
juliusv commentedJun 20, 2013
This becomes relevant for large labelsets, even if they only map to a single timeseries: looking up the fingerprints for the labelset then takes the majority of time (e.g. 70ms of 76ms total query time).
Every time we do this lookup, we go out to both disk and memory. We should probably cache these lookups in memory too.