2013-02-08 09:03:26 -08:00
|
|
|
// Copyright 2013 Prometheus Team
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
//
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
|
|
|
|
2014-04-11 00:27:05 -07:00
|
|
|
package tiered
|
2013-02-08 09:03:26 -08:00
|
|
|
|
|
|
|
import (
|
Remove the multi-op-per-fingerprint capability.
Currently, rendering a view is capable of handling multiple ops for
the same fingerprint efficiently. However, this capability requires a
lot of complexity in the code, which we are not using at all because
the way we assemble a viewRequest will never have more than one
operation per fingerprint.
This commit weeds out the said capability, along with all the code
needed for it. It is still possible to have more than one operation
for the same fingerprint, it will just be handled in a less efficient
way (as proven by the unit tests).
As a result, scanjob.go could be removed entirely.
This commit also contains a few related refactorings and removals of
dead code in operation.go, view,go, and freelist.go. Also, the
docstrings received some love.
Change-Id: I032b976e0880151c3f3fdb3234fb65e484f0e2e5
2014-02-27 11:09:00 -08:00
|
|
|
"container/heap"
|
2013-02-08 09:03:26 -08:00
|
|
|
"time"
|
2013-06-19 06:00:00 -07:00
|
|
|
|
2013-06-25 05:02:27 -07:00
|
|
|
clientmodel "github.com/prometheus/client_golang/model"
|
2013-02-08 09:03:26 -08:00
|
|
|
|
2014-04-11 00:27:05 -07:00
|
|
|
"github.com/prometheus/prometheus/stats"
|
|
|
|
"github.com/prometheus/prometheus/storage/metric"
|
2013-02-08 09:03:26 -08:00
|
|
|
)
|
|
|
|
|
Remove the multi-op-per-fingerprint capability.
Currently, rendering a view is capable of handling multiple ops for
the same fingerprint efficiently. However, this capability requires a
lot of complexity in the code, which we are not using at all because
the way we assemble a viewRequest will never have more than one
operation per fingerprint.
This commit weeds out the said capability, along with all the code
needed for it. It is still possible to have more than one operation
for the same fingerprint, it will just be handled in a less efficient
way (as proven by the unit tests).
As a result, scanjob.go could be removed entirely.
This commit also contains a few related refactorings and removals of
dead code in operation.go, view,go, and freelist.go. Also, the
docstrings received some love.
Change-Id: I032b976e0880151c3f3fdb3234fb65e484f0e2e5
2014-02-27 11:09:00 -08:00
|
|
|
// viewRequestBuilder contains the various requests for data.
|
2013-02-08 09:03:26 -08:00
|
|
|
type viewRequestBuilder struct {
|
2014-04-11 00:27:05 -07:00
|
|
|
storage *TieredStorage
|
Remove the multi-op-per-fingerprint capability.
Currently, rendering a view is capable of handling multiple ops for
the same fingerprint efficiently. However, this capability requires a
lot of complexity in the code, which we are not using at all because
the way we assemble a viewRequest will never have more than one
operation per fingerprint.
This commit weeds out the said capability, along with all the code
needed for it. It is still possible to have more than one operation
for the same fingerprint, it will just be handled in a less efficient
way (as proven by the unit tests).
As a result, scanjob.go could be removed entirely.
This commit also contains a few related refactorings and removals of
dead code in operation.go, view,go, and freelist.go. Also, the
docstrings received some love.
Change-Id: I032b976e0880151c3f3fdb3234fb65e484f0e2e5
2014-02-27 11:09:00 -08:00
|
|
|
operations ops
|
2013-02-08 09:03:26 -08:00
|
|
|
}
|
|
|
|
|
2013-08-29 06:15:22 -07:00
|
|
|
var getValuesAtTimes = newValueAtTimeList(10 * 1024)
|
|
|
|
|
Remove the multi-op-per-fingerprint capability.
Currently, rendering a view is capable of handling multiple ops for
the same fingerprint efficiently. However, this capability requires a
lot of complexity in the code, which we are not using at all because
the way we assemble a viewRequest will never have more than one
operation per fingerprint.
This commit weeds out the said capability, along with all the code
needed for it. It is still possible to have more than one operation
for the same fingerprint, it will just be handled in a less efficient
way (as proven by the unit tests).
As a result, scanjob.go could be removed entirely.
This commit also contains a few related refactorings and removals of
dead code in operation.go, view,go, and freelist.go. Also, the
docstrings received some love.
Change-Id: I032b976e0880151c3f3fdb3234fb65e484f0e2e5
2014-02-27 11:09:00 -08:00
|
|
|
// GetMetricAtTime implements ViewRequestBuilder.
|
|
|
|
func (v *viewRequestBuilder) GetMetricAtTime(fp *clientmodel.Fingerprint, time clientmodel.Timestamp) {
|
|
|
|
heap.Push(&v.operations, getValuesAtTimes.Get(fp, time))
|
2013-02-08 09:03:26 -08:00
|
|
|
}
|
|
|
|
|
2013-08-29 06:15:22 -07:00
|
|
|
var getValuesAtIntervals = newValueAtIntervalList(10 * 1024)
|
|
|
|
|
Remove the multi-op-per-fingerprint capability.
Currently, rendering a view is capable of handling multiple ops for
the same fingerprint efficiently. However, this capability requires a
lot of complexity in the code, which we are not using at all because
the way we assemble a viewRequest will never have more than one
operation per fingerprint.
This commit weeds out the said capability, along with all the code
needed for it. It is still possible to have more than one operation
for the same fingerprint, it will just be handled in a less efficient
way (as proven by the unit tests).
As a result, scanjob.go could be removed entirely.
This commit also contains a few related refactorings and removals of
dead code in operation.go, view,go, and freelist.go. Also, the
docstrings received some love.
Change-Id: I032b976e0880151c3f3fdb3234fb65e484f0e2e5
2014-02-27 11:09:00 -08:00
|
|
|
// GetMetricAtInterval implements ViewRequestBuilder.
|
|
|
|
func (v *viewRequestBuilder) GetMetricAtInterval(fp *clientmodel.Fingerprint, from, through clientmodel.Timestamp, interval time.Duration) {
|
|
|
|
heap.Push(&v.operations, getValuesAtIntervals.Get(fp, from, through, interval))
|
2013-02-08 09:03:26 -08:00
|
|
|
}
|
|
|
|
|
2013-08-29 06:15:22 -07:00
|
|
|
var getValuesAlongRanges = newValueAlongRangeList(10 * 1024)
|
|
|
|
|
Remove the multi-op-per-fingerprint capability.
Currently, rendering a view is capable of handling multiple ops for
the same fingerprint efficiently. However, this capability requires a
lot of complexity in the code, which we are not using at all because
the way we assemble a viewRequest will never have more than one
operation per fingerprint.
This commit weeds out the said capability, along with all the code
needed for it. It is still possible to have more than one operation
for the same fingerprint, it will just be handled in a less efficient
way (as proven by the unit tests).
As a result, scanjob.go could be removed entirely.
This commit also contains a few related refactorings and removals of
dead code in operation.go, view,go, and freelist.go. Also, the
docstrings received some love.
Change-Id: I032b976e0880151c3f3fdb3234fb65e484f0e2e5
2014-02-27 11:09:00 -08:00
|
|
|
// GetMetricRange implements ViewRequestBuilder.
|
|
|
|
func (v *viewRequestBuilder) GetMetricRange(fp *clientmodel.Fingerprint, from, through clientmodel.Timestamp) {
|
|
|
|
heap.Push(&v.operations, getValuesAlongRanges.Get(fp, from, through))
|
2013-02-08 09:03:26 -08:00
|
|
|
}
|
|
|
|
|
2013-08-29 06:15:22 -07:00
|
|
|
var getValuesAtIntervalAlongRanges = newValueAtIntervalAlongRangeList(10 * 1024)
|
|
|
|
|
Remove the multi-op-per-fingerprint capability.
Currently, rendering a view is capable of handling multiple ops for
the same fingerprint efficiently. However, this capability requires a
lot of complexity in the code, which we are not using at all because
the way we assemble a viewRequest will never have more than one
operation per fingerprint.
This commit weeds out the said capability, along with all the code
needed for it. It is still possible to have more than one operation
for the same fingerprint, it will just be handled in a less efficient
way (as proven by the unit tests).
As a result, scanjob.go could be removed entirely.
This commit also contains a few related refactorings and removals of
dead code in operation.go, view,go, and freelist.go. Also, the
docstrings received some love.
Change-Id: I032b976e0880151c3f3fdb3234fb65e484f0e2e5
2014-02-27 11:09:00 -08:00
|
|
|
// GetMetricRangeAtInterval implements ViewRequestBuilder.
|
|
|
|
func (v *viewRequestBuilder) GetMetricRangeAtInterval(fp *clientmodel.Fingerprint, from, through clientmodel.Timestamp, interval, rangeDuration time.Duration) {
|
|
|
|
heap.Push(&v.operations, getValuesAtIntervalAlongRanges.Get(fp, from, through, interval, rangeDuration))
|
2013-05-07 05:25:01 -07:00
|
|
|
}
|
|
|
|
|
2014-04-11 00:27:05 -07:00
|
|
|
// Execute implements ViewRequestBuilder.
|
|
|
|
func (v *viewRequestBuilder) Execute(deadline time.Duration, queryStats *stats.TimerGroup) (metric.View, error) {
|
|
|
|
return v.storage.makeView(v, deadline, queryStats)
|
|
|
|
}
|
|
|
|
|
Remove the multi-op-per-fingerprint capability.
Currently, rendering a view is capable of handling multiple ops for
the same fingerprint efficiently. However, this capability requires a
lot of complexity in the code, which we are not using at all because
the way we assemble a viewRequest will never have more than one
operation per fingerprint.
This commit weeds out the said capability, along with all the code
needed for it. It is still possible to have more than one operation
for the same fingerprint, it will just be handled in a less efficient
way (as proven by the unit tests).
As a result, scanjob.go could be removed entirely.
This commit also contains a few related refactorings and removals of
dead code in operation.go, view,go, and freelist.go. Also, the
docstrings received some love.
Change-Id: I032b976e0880151c3f3fdb3234fb65e484f0e2e5
2014-02-27 11:09:00 -08:00
|
|
|
// PopOp implements ViewRequestBuilder.
|
2014-04-11 00:27:05 -07:00
|
|
|
func (v *viewRequestBuilder) PopOp() metric.Op {
|
|
|
|
return heap.Pop(&v.operations).(metric.Op)
|
Remove the multi-op-per-fingerprint capability.
Currently, rendering a view is capable of handling multiple ops for
the same fingerprint efficiently. However, this capability requires a
lot of complexity in the code, which we are not using at all because
the way we assemble a viewRequest will never have more than one
operation per fingerprint.
This commit weeds out the said capability, along with all the code
needed for it. It is still possible to have more than one operation
for the same fingerprint, it will just be handled in a less efficient
way (as proven by the unit tests).
As a result, scanjob.go could be removed entirely.
This commit also contains a few related refactorings and removals of
dead code in operation.go, view,go, and freelist.go. Also, the
docstrings received some love.
Change-Id: I032b976e0880151c3f3fdb3234fb65e484f0e2e5
2014-02-27 11:09:00 -08:00
|
|
|
}
|
2013-02-08 09:03:26 -08:00
|
|
|
|
Remove the multi-op-per-fingerprint capability.
Currently, rendering a view is capable of handling multiple ops for
the same fingerprint efficiently. However, this capability requires a
lot of complexity in the code, which we are not using at all because
the way we assemble a viewRequest will never have more than one
operation per fingerprint.
This commit weeds out the said capability, along with all the code
needed for it. It is still possible to have more than one operation
for the same fingerprint, it will just be handled in a less efficient
way (as proven by the unit tests).
As a result, scanjob.go could be removed entirely.
This commit also contains a few related refactorings and removals of
dead code in operation.go, view,go, and freelist.go. Also, the
docstrings received some love.
Change-Id: I032b976e0880151c3f3fdb3234fb65e484f0e2e5
2014-02-27 11:09:00 -08:00
|
|
|
// HasOp implements ViewRequestBuilder.
|
|
|
|
func (v *viewRequestBuilder) HasOp() bool {
|
|
|
|
return v.operations.Len() > 0
|
2013-02-08 09:03:26 -08:00
|
|
|
}
|
2013-03-06 17:16:39 -08:00
|
|
|
|
|
|
|
type view struct {
|
2013-05-16 07:02:07 -07:00
|
|
|
*memorySeriesStorage
|
2013-03-06 17:16:39 -08:00
|
|
|
}
|
|
|
|
|
2014-04-11 00:27:05 -07:00
|
|
|
func (v view) appendSamples(fingerprint *clientmodel.Fingerprint, samples metric.Values) {
|
2013-05-28 05:36:03 -07:00
|
|
|
v.memorySeriesStorage.appendSamplesWithoutIndexing(fingerprint, samples)
|
2013-03-06 17:16:39 -08:00
|
|
|
}
|
|
|
|
|
|
|
|
func newView() view {
|
2013-06-06 09:16:22 -07:00
|
|
|
return view{NewMemorySeriesStorage(MemorySeriesOptions{})}
|
2013-03-06 17:16:39 -08:00
|
|
|
}
|
2013-08-29 06:15:22 -07:00
|
|
|
|
|
|
|
func giveBackOp(op interface{}) bool {
|
|
|
|
switch v := op.(type) {
|
|
|
|
case *getValuesAtTimeOp:
|
|
|
|
return getValuesAtTimes.Give(v)
|
|
|
|
case *getValuesAtIntervalOp:
|
|
|
|
return getValuesAtIntervals.Give(v)
|
|
|
|
case *getValuesAlongRangeOp:
|
|
|
|
return getValuesAlongRanges.Give(v)
|
|
|
|
case *getValueRangeAtIntervalOp:
|
|
|
|
return getValuesAtIntervalAlongRanges.Give(v)
|
|
|
|
default:
|
|
|
|
panic("unrecognized operation")
|
|
|
|
}
|
|
|
|
}
|