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 upAdd operator that supports getting ranges at intervals #89
Comments
ghost
assigned
matttproud
Mar 21, 2013
This comment has been minimized.
This comment has been minimized.
|
Also, having one range-at-interval-op for each entire timeseries is going to be faster and more memory-efficient than one per target point in the timeseries. |
This comment has been minimized.
This comment has been minimized.
|
Operator implemented in d2da211 - disabled optimize() phase... we might have to revisit whether to keep/properly implement the optimization phase later, so keeping this open for now. |
This comment has been minimized.
This comment has been minimized.
|
We decided we'll not need the optimize() phase again, so closing this. |
juliusv
closed this
May 23, 2014
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 commentedMar 21, 2013
If a query resolution is lower (e.g. 5m) than a metric range (like foo[1m]) requested in a query, we actually need to fetch ranges at repeated intervals so as not to fetch too much data.