2020-03-24 07:41:10 +02:00
|
|
|
// Copyright The OpenTelemetry Authors
|
2019-10-29 22:27:22 +02:00
|
|
|
//
|
|
|
|
// 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.
|
|
|
|
|
|
|
|
package metric
|
|
|
|
|
|
|
|
import (
|
|
|
|
"context"
|
2019-11-15 23:01:20 +02:00
|
|
|
"fmt"
|
|
|
|
"os"
|
2020-03-11 18:11:27 +02:00
|
|
|
"reflect"
|
2020-02-11 02:20:29 +02:00
|
|
|
"runtime"
|
2019-10-29 22:27:22 +02:00
|
|
|
"sort"
|
|
|
|
"sync"
|
|
|
|
"sync/atomic"
|
|
|
|
|
2019-11-01 20:40:29 +02:00
|
|
|
"go.opentelemetry.io/otel/api/core"
|
|
|
|
"go.opentelemetry.io/otel/api/metric"
|
|
|
|
api "go.opentelemetry.io/otel/api/metric"
|
2019-11-05 23:08:55 +02:00
|
|
|
export "go.opentelemetry.io/otel/sdk/export/metric"
|
2019-11-15 23:01:20 +02:00
|
|
|
"go.opentelemetry.io/otel/sdk/export/metric/aggregator"
|
2020-03-20 17:58:32 +02:00
|
|
|
"go.opentelemetry.io/otel/sdk/resource"
|
2019-10-29 22:27:22 +02:00
|
|
|
)
|
|
|
|
|
|
|
|
type (
|
|
|
|
// SDK implements the OpenTelemetry Meter API. The SDK is
|
2019-11-15 23:01:20 +02:00
|
|
|
// bound to a single export.Batcher in `New()`.
|
2019-10-29 22:27:22 +02:00
|
|
|
//
|
|
|
|
// The SDK supports a Collect() API to gather and export
|
|
|
|
// current data. Collect() should be arranged according to
|
2019-11-15 23:01:20 +02:00
|
|
|
// the batcher model. Push-based batchers will setup a
|
|
|
|
// timer to call Collect() periodically. Pull-based batchers
|
2019-10-29 22:27:22 +02:00
|
|
|
// will call Collect() when a pull request arrives.
|
|
|
|
SDK struct {
|
|
|
|
// current maps `mapkey` to *record.
|
|
|
|
current sync.Map
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
// asyncInstruments is a set of
|
|
|
|
// `*asyncInstrument` instances
|
|
|
|
asyncInstruments sync.Map
|
2020-03-05 22:15:30 +02:00
|
|
|
|
2019-10-29 22:27:22 +02:00
|
|
|
// empty is the (singleton) result of Labels()
|
|
|
|
// w/ zero arguments.
|
|
|
|
empty labels
|
|
|
|
|
|
|
|
// currentEpoch is the current epoch number. It is
|
|
|
|
// incremented in `Collect()`.
|
|
|
|
currentEpoch int64
|
|
|
|
|
2019-11-15 23:01:20 +02:00
|
|
|
// batcher is the configured batcher+configuration.
|
|
|
|
batcher export.Batcher
|
|
|
|
|
|
|
|
// lencoder determines how labels are uniquely encoded.
|
|
|
|
labelEncoder export.LabelEncoder
|
2019-10-29 22:27:22 +02:00
|
|
|
|
|
|
|
// collectLock prevents simultaneous calls to Collect().
|
|
|
|
collectLock sync.Mutex
|
2019-11-15 23:01:20 +02:00
|
|
|
|
|
|
|
// errorHandler supports delivering errors to the user.
|
|
|
|
errorHandler ErrorHandler
|
2020-03-20 17:58:32 +02:00
|
|
|
|
|
|
|
// resource represents the entity producing telemetry.
|
|
|
|
resource resource.Resource
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
syncInstrument struct {
|
|
|
|
instrument
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
2020-03-11 18:11:27 +02:00
|
|
|
// orderedLabels is a variable-size array of core.KeyValue
|
|
|
|
// suitable for use as a map key.
|
|
|
|
orderedLabels interface{}
|
2019-10-29 22:27:22 +02:00
|
|
|
|
|
|
|
// labels implements the OpenTelemetry LabelSet API,
|
|
|
|
// represents an internalized set of labels that may be used
|
|
|
|
// repeatedly.
|
|
|
|
labels struct {
|
2020-03-11 18:11:27 +02:00
|
|
|
meter *SDK
|
|
|
|
// ordered is the output of sorting and deduplicating
|
|
|
|
// the labels, copied into an array of the correct
|
|
|
|
// size for use as a map key.
|
|
|
|
ordered orderedLabels
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
|
|
|
|
// sortSlice has a single purpose - as a temporary
|
|
|
|
// place for sorting during labels creation to avoid
|
|
|
|
// allocation
|
|
|
|
sortSlice sortedLabels
|
|
|
|
// cachedValue contains a `reflect.Value` of the `ordered`
|
|
|
|
// member
|
|
|
|
cachedValue reflect.Value
|
2020-03-20 18:17:45 +02:00
|
|
|
// cachedEncoded contains an encoded version of the
|
|
|
|
// `ordered` member
|
|
|
|
cachedEncoded string
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
// mapkey uniquely describes a metric instrument in terms of
|
|
|
|
// its InstrumentID and the encoded form of its LabelSet.
|
|
|
|
mapkey struct {
|
2020-03-19 21:02:46 +02:00
|
|
|
descriptor *metric.Descriptor
|
2020-03-11 18:11:27 +02:00
|
|
|
ordered orderedLabels
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
// record maintains the state of one metric instrument. Due
|
|
|
|
// the use of lock-free algorithms, there may be more than one
|
|
|
|
// `record` in existence at a time, although at most one can
|
|
|
|
// be referenced from the `SDK.current` map.
|
|
|
|
record struct {
|
2020-02-07 00:45:56 +02:00
|
|
|
// refMapped keeps track of refcounts and the mapping state to the
|
|
|
|
// SDK.current map.
|
|
|
|
refMapped refcountMapped
|
2019-10-29 22:27:22 +02:00
|
|
|
|
2020-02-07 00:45:56 +02:00
|
|
|
// modified is an atomic boolean that tracks if the current record
|
|
|
|
// was modified since the last Collect().
|
2020-01-06 20:08:40 +02:00
|
|
|
//
|
2020-02-07 00:45:56 +02:00
|
|
|
// modified has to be aligned for 64-bit atomic operations.
|
|
|
|
modified int64
|
2019-10-29 22:27:22 +02:00
|
|
|
|
2020-01-06 20:08:40 +02:00
|
|
|
// labels is the LabelSet passed by the user.
|
|
|
|
labels *labels
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
// inst is a pointer to the corresponding instrument.
|
|
|
|
inst *syncInstrument
|
2020-01-06 20:08:40 +02:00
|
|
|
|
2019-10-29 22:27:22 +02:00
|
|
|
// recorder implements the actual RecordOne() API,
|
|
|
|
// depending on the type of aggregation. If nil, the
|
|
|
|
// metric was disabled by the exporter.
|
2019-11-05 23:08:55 +02:00
|
|
|
recorder export.Aggregator
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
instrument struct {
|
|
|
|
meter *SDK
|
|
|
|
descriptor metric.Descriptor
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
asyncInstrument struct {
|
|
|
|
instrument
|
2020-03-11 18:11:27 +02:00
|
|
|
// recorders maps ordered labels to the pair of
|
2020-03-05 22:15:30 +02:00
|
|
|
// labelset and recorder
|
2020-03-11 18:11:27 +02:00
|
|
|
recorders map[orderedLabels]labeledRecorder
|
2020-03-19 21:02:46 +02:00
|
|
|
|
|
|
|
callback func(func(core.Number, api.LabelSet))
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
labeledRecorder struct {
|
|
|
|
recorder export.Aggregator
|
|
|
|
labels *labels
|
|
|
|
modifiedEpoch int64
|
|
|
|
}
|
|
|
|
|
2019-11-15 23:01:20 +02:00
|
|
|
ErrorHandler func(error)
|
2019-10-29 22:27:22 +02:00
|
|
|
)
|
|
|
|
|
|
|
|
var (
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
_ api.MeterImpl = &SDK{}
|
|
|
|
_ api.LabelSet = &labels{}
|
|
|
|
_ api.AsyncImpl = &asyncInstrument{}
|
|
|
|
_ api.SyncImpl = &syncInstrument{}
|
|
|
|
_ api.BoundSyncImpl = &record{}
|
2020-03-20 17:58:32 +02:00
|
|
|
_ api.Resourcer = &SDK{}
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
_ export.LabelStorage = &labels{}
|
2020-03-11 18:11:27 +02:00
|
|
|
|
|
|
|
kvType = reflect.TypeOf(core.KeyValue{})
|
2019-10-29 22:27:22 +02:00
|
|
|
)
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (inst *instrument) Descriptor() api.Descriptor {
|
|
|
|
return inst.descriptor
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (a *asyncInstrument) Implementation() interface{} {
|
|
|
|
return a
|
|
|
|
}
|
|
|
|
|
|
|
|
func (s *syncInstrument) Implementation() interface{} {
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
func (a *asyncInstrument) observe(number core.Number, ls api.LabelSet) {
|
|
|
|
if err := aggregator.RangeTest(number, &a.descriptor); err != nil {
|
|
|
|
a.meter.errorHandler(err)
|
2020-03-05 22:15:30 +02:00
|
|
|
return
|
|
|
|
}
|
2020-03-19 21:02:46 +02:00
|
|
|
recorder := a.getRecorder(ls)
|
2020-03-05 22:15:30 +02:00
|
|
|
if recorder == nil {
|
|
|
|
// The instrument is disabled according to the
|
|
|
|
// AggregationSelector.
|
|
|
|
return
|
|
|
|
}
|
2020-03-19 21:02:46 +02:00
|
|
|
if err := recorder.Update(context.Background(), number, &a.descriptor); err != nil {
|
|
|
|
a.meter.errorHandler(err)
|
2020-03-05 22:15:30 +02:00
|
|
|
return
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (a *asyncInstrument) getRecorder(ls api.LabelSet) export.Aggregator {
|
|
|
|
labels := a.meter.labsFor(ls)
|
|
|
|
lrec, ok := a.recorders[labels.ordered]
|
2020-03-05 22:15:30 +02:00
|
|
|
if ok {
|
2020-03-19 21:02:46 +02:00
|
|
|
lrec.modifiedEpoch = a.meter.currentEpoch
|
|
|
|
a.recorders[labels.ordered] = lrec
|
2020-03-05 22:15:30 +02:00
|
|
|
return lrec.recorder
|
|
|
|
}
|
2020-03-19 21:02:46 +02:00
|
|
|
rec := a.meter.batcher.AggregatorFor(&a.descriptor)
|
|
|
|
if a.recorders == nil {
|
|
|
|
a.recorders = make(map[orderedLabels]labeledRecorder)
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
|
|
|
// This may store nil recorder in the map, thus disabling the
|
2020-03-19 21:02:46 +02:00
|
|
|
// asyncInstrument for the labelset for good. This is intentional,
|
2020-03-05 22:15:30 +02:00
|
|
|
// but will be revisited later.
|
2020-03-19 21:02:46 +02:00
|
|
|
a.recorders[labels.ordered] = labeledRecorder{
|
2020-03-05 22:15:30 +02:00
|
|
|
recorder: rec,
|
|
|
|
labels: labels,
|
2020-03-19 21:02:46 +02:00
|
|
|
modifiedEpoch: a.meter.currentEpoch,
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
|
|
|
return rec
|
|
|
|
}
|
|
|
|
|
2019-11-15 23:01:20 +02:00
|
|
|
func (m *SDK) SetErrorHandler(f ErrorHandler) {
|
|
|
|
m.errorHandler = f
|
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (s *syncInstrument) acquireHandle(ls *labels) *record {
|
2019-11-06 20:54:36 +02:00
|
|
|
// Create lookup key for sync.Map (one allocation)
|
2019-10-29 22:27:22 +02:00
|
|
|
mk := mapkey{
|
2020-03-19 21:02:46 +02:00
|
|
|
descriptor: &s.descriptor,
|
2020-03-11 18:11:27 +02:00
|
|
|
ordered: ls.ordered,
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
if actual, ok := s.meter.current.Load(mk); ok {
|
2019-11-06 20:54:36 +02:00
|
|
|
// Existing record case, only one allocation so far.
|
|
|
|
rec := actual.(*record)
|
2020-02-07 00:45:56 +02:00
|
|
|
if rec.refMapped.ref() {
|
|
|
|
// At this moment it is guaranteed that the entry is in
|
|
|
|
// the map and will not be removed.
|
|
|
|
return rec
|
|
|
|
}
|
|
|
|
// This entry is no longer mapped, try to add a new entry.
|
2019-11-06 20:54:36 +02:00
|
|
|
}
|
|
|
|
|
2019-10-29 22:27:22 +02:00
|
|
|
// There's a memory allocation here.
|
|
|
|
rec := &record{
|
2020-03-19 21:02:46 +02:00
|
|
|
labels: ls,
|
|
|
|
inst: s,
|
|
|
|
refMapped: refcountMapped{value: 2},
|
|
|
|
modified: 0,
|
|
|
|
recorder: s.meter.batcher.AggregatorFor(&s.descriptor),
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
2020-02-07 00:45:56 +02:00
|
|
|
for {
|
|
|
|
// Load/Store: there's a memory allocation to place `mk` into
|
|
|
|
// an interface here.
|
2020-03-19 21:02:46 +02:00
|
|
|
if actual, loaded := s.meter.current.LoadOrStore(mk, rec); loaded {
|
2020-02-07 00:45:56 +02:00
|
|
|
// Existing record case. Cannot change rec here because if fail
|
|
|
|
// will try to add rec again to avoid new allocations.
|
|
|
|
oldRec := actual.(*record)
|
|
|
|
if oldRec.refMapped.ref() {
|
|
|
|
// At this moment it is guaranteed that the entry is in
|
|
|
|
// the map and will not be removed.
|
|
|
|
return oldRec
|
|
|
|
}
|
|
|
|
// This loaded entry is marked as unmapped (so Collect will remove
|
|
|
|
// it from the map immediately), try again - this is a busy waiting
|
|
|
|
// strategy to wait until Collect() removes this entry from the map.
|
|
|
|
//
|
|
|
|
// This can be improved by having a list of "Unmapped" entries for
|
|
|
|
// one time only usages, OR we can make this a blocking path and use
|
|
|
|
// a Mutex that protects the delete operation (delete only if the old
|
|
|
|
// record is associated with the key).
|
2020-02-11 02:20:29 +02:00
|
|
|
|
|
|
|
// Let collector get work done to remove the entry from the map.
|
|
|
|
runtime.Gosched()
|
2020-02-07 00:45:56 +02:00
|
|
|
continue
|
|
|
|
}
|
|
|
|
// The new entry was added to the map, good to go.
|
2019-10-29 22:27:22 +02:00
|
|
|
return rec
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (s *syncInstrument) Bind(ls api.LabelSet) api.BoundSyncImpl {
|
|
|
|
labs := s.meter.labsFor(ls)
|
|
|
|
return s.acquireHandle(labs)
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (s *syncInstrument) RecordOne(ctx context.Context, number core.Number, ls api.LabelSet) {
|
|
|
|
ourLs := s.meter.labsFor(ls)
|
|
|
|
h := s.acquireHandle(ourLs)
|
2019-12-28 02:30:19 +02:00
|
|
|
defer h.Unbind()
|
2019-10-29 22:27:22 +02:00
|
|
|
h.RecordOne(ctx, number)
|
|
|
|
}
|
|
|
|
|
2019-11-15 23:01:20 +02:00
|
|
|
// New constructs a new SDK for the given batcher. This SDK supports
|
|
|
|
// only a single batcher.
|
2019-10-29 22:27:22 +02:00
|
|
|
//
|
|
|
|
// The SDK does not start any background process to collect itself
|
2019-11-15 23:01:20 +02:00
|
|
|
// periodically, this responsbility lies with the batcher, typically,
|
2019-10-29 22:27:22 +02:00
|
|
|
// depending on the type of export. For example, a pull-based
|
2019-11-15 23:01:20 +02:00
|
|
|
// batcher will call Collect() when it receives a request to scrape
|
|
|
|
// current metric values. A push-based batcher should configure its
|
2019-10-29 22:27:22 +02:00
|
|
|
// own periodic collection.
|
2020-03-20 17:58:32 +02:00
|
|
|
func New(batcher export.Batcher, labelEncoder export.LabelEncoder, opts ...Option) *SDK {
|
|
|
|
c := &Config{ErrorHandler: DefaultErrorHandler}
|
|
|
|
for _, opt := range opts {
|
|
|
|
opt.Apply(c)
|
|
|
|
}
|
|
|
|
|
2019-10-29 22:27:22 +02:00
|
|
|
m := &SDK{
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
empty: labels{
|
|
|
|
ordered: [0]core.KeyValue{},
|
|
|
|
},
|
2019-11-15 23:01:20 +02:00
|
|
|
batcher: batcher,
|
|
|
|
labelEncoder: labelEncoder,
|
2020-03-20 17:58:32 +02:00
|
|
|
errorHandler: c.ErrorHandler,
|
|
|
|
resource: c.Resource,
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
m.empty.meter = m
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
m.empty.cachedValue = reflect.ValueOf(m.empty.ordered)
|
2019-10-29 22:27:22 +02:00
|
|
|
return m
|
|
|
|
}
|
|
|
|
|
2019-11-15 23:01:20 +02:00
|
|
|
func DefaultErrorHandler(err error) {
|
|
|
|
fmt.Fprintln(os.Stderr, "Metrics SDK error:", err)
|
|
|
|
}
|
|
|
|
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
// Labels returns a LabelSet corresponding to the arguments. Passed labels
|
|
|
|
// are sorted and de-duplicated, with last-value-wins semantics. Note that
|
|
|
|
// sorting and deduplicating happens in-place to avoid allocation, so the
|
|
|
|
// passed slice will be modified.
|
2019-10-29 22:27:22 +02:00
|
|
|
func (m *SDK) Labels(kvs ...core.KeyValue) api.LabelSet {
|
|
|
|
// Check for empty set.
|
|
|
|
if len(kvs) == 0 {
|
|
|
|
return &m.empty
|
|
|
|
}
|
|
|
|
|
2020-03-11 18:11:27 +02:00
|
|
|
ls := &labels{ // allocation
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
meter: m,
|
|
|
|
sortSlice: kvs,
|
2019-11-14 23:13:42 +02:00
|
|
|
}
|
|
|
|
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
// Sort and de-duplicate. Note: this use of `ls.sortSlice`
|
|
|
|
// avoids an allocation by using the address-able field rather
|
|
|
|
// than `kvs`.
|
|
|
|
sort.Stable(&ls.sortSlice)
|
|
|
|
ls.sortSlice = nil
|
2020-03-11 18:11:27 +02:00
|
|
|
|
2019-10-29 22:27:22 +02:00
|
|
|
oi := 1
|
2020-03-11 18:11:27 +02:00
|
|
|
for i := 1; i < len(kvs); i++ {
|
|
|
|
if kvs[i-1].Key == kvs[i].Key {
|
|
|
|
// Overwrite the value for "last-value wins".
|
|
|
|
kvs[oi-1].Value = kvs[i].Value
|
2019-10-29 22:27:22 +02:00
|
|
|
continue
|
|
|
|
}
|
2020-03-11 18:11:27 +02:00
|
|
|
kvs[oi] = kvs[i]
|
2019-10-29 22:27:22 +02:00
|
|
|
oi++
|
|
|
|
}
|
2020-03-11 18:11:27 +02:00
|
|
|
kvs = kvs[0:oi]
|
|
|
|
ls.computeOrdered(kvs)
|
|
|
|
return ls
|
|
|
|
}
|
2019-10-29 22:27:22 +02:00
|
|
|
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
func (ls *labels) NumLabels() int {
|
|
|
|
return ls.cachedValue.Len()
|
|
|
|
}
|
|
|
|
|
|
|
|
func (ls *labels) GetLabel(idx int) core.KeyValue {
|
|
|
|
return ls.cachedValue.Index(idx).Interface().(core.KeyValue)
|
|
|
|
}
|
|
|
|
|
2020-03-11 18:11:27 +02:00
|
|
|
func (ls *labels) computeOrdered(kvs []core.KeyValue) {
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
ls.ordered = computeOrderedFixed(kvs)
|
|
|
|
if ls.ordered == nil {
|
|
|
|
ls.ordered = computeOrderedReflect(kvs)
|
|
|
|
}
|
|
|
|
ls.cachedValue = reflect.ValueOf(ls.ordered)
|
|
|
|
}
|
|
|
|
|
2020-03-20 18:17:45 +02:00
|
|
|
func (ls *labels) ensureEncoded(encoder export.LabelEncoder) {
|
|
|
|
if ls.cachedEncoded != "" {
|
|
|
|
return
|
|
|
|
}
|
|
|
|
iter := export.NewLabelIterator(ls)
|
|
|
|
ls.cachedEncoded = encoder.Encode(iter)
|
|
|
|
}
|
|
|
|
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
func computeOrderedFixed(kvs []core.KeyValue) orderedLabels {
|
2020-03-11 18:11:27 +02:00
|
|
|
switch len(kvs) {
|
|
|
|
case 1:
|
|
|
|
ptr := new([1]core.KeyValue)
|
|
|
|
copy((*ptr)[:], kvs)
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return *ptr
|
2020-03-11 18:11:27 +02:00
|
|
|
case 2:
|
|
|
|
ptr := new([2]core.KeyValue)
|
|
|
|
copy((*ptr)[:], kvs)
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return *ptr
|
2020-03-11 18:11:27 +02:00
|
|
|
case 3:
|
|
|
|
ptr := new([3]core.KeyValue)
|
|
|
|
copy((*ptr)[:], kvs)
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return *ptr
|
2020-03-11 18:11:27 +02:00
|
|
|
case 4:
|
|
|
|
ptr := new([4]core.KeyValue)
|
|
|
|
copy((*ptr)[:], kvs)
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return *ptr
|
2020-03-11 18:11:27 +02:00
|
|
|
case 5:
|
|
|
|
ptr := new([5]core.KeyValue)
|
|
|
|
copy((*ptr)[:], kvs)
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return *ptr
|
2020-03-11 18:11:27 +02:00
|
|
|
case 6:
|
|
|
|
ptr := new([6]core.KeyValue)
|
|
|
|
copy((*ptr)[:], kvs)
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return *ptr
|
2020-03-11 18:11:27 +02:00
|
|
|
case 7:
|
|
|
|
ptr := new([7]core.KeyValue)
|
|
|
|
copy((*ptr)[:], kvs)
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return *ptr
|
2020-03-11 18:11:27 +02:00
|
|
|
case 8:
|
|
|
|
ptr := new([8]core.KeyValue)
|
|
|
|
copy((*ptr)[:], kvs)
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return *ptr
|
2020-03-11 18:11:27 +02:00
|
|
|
case 9:
|
|
|
|
ptr := new([9]core.KeyValue)
|
|
|
|
copy((*ptr)[:], kvs)
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return *ptr
|
2020-03-11 18:11:27 +02:00
|
|
|
case 10:
|
|
|
|
ptr := new([10]core.KeyValue)
|
|
|
|
copy((*ptr)[:], kvs)
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return *ptr
|
2020-03-11 18:11:27 +02:00
|
|
|
default:
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return nil
|
|
|
|
}
|
|
|
|
}
|
2019-11-14 23:13:42 +02:00
|
|
|
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
func computeOrderedReflect(kvs []core.KeyValue) interface{} {
|
|
|
|
at := reflect.New(reflect.ArrayOf(len(kvs), kvType)).Elem()
|
|
|
|
for i, kv := range kvs {
|
|
|
|
*(at.Index(i).Addr().Interface().(*core.KeyValue)) = kv
|
2020-03-11 18:11:27 +02:00
|
|
|
}
|
Replace `Ordered` with an iterator in `export.Labels`. (#567)
* Do not expose a slice of labels in export.Record
This is really an inconvenient implementation detail leak - we may
want to store labels in a different way. Replace it with an iterator -
it does not force us to use slice of key values as a storage in the
long run.
* Add Len to LabelIterator
It may come in handy in several situations, where we don't have access
to export.Labels object, but only to the label iterator.
* Use reflect value label iterator for the fixed labels
* add reset operation to iterator
Makes my life easier when writing a benchmark. Might also be an
alternative to cloning the iterator.
* Add benchmarks for iterators
* Add import comment
* Add clone operation to label iterator
* Move iterator tests to a separate package
* Add tests for cloning iterators
* Pass label iterator to export labels
* Use non-addressable array reflect values
By not using the value created by `reflect.New()`, but rather by
`reflect.ValueOf()`, we get a non-addressable array in the value,
which does not infer an allocation cost when getting an element from
the array.
* Drop zero iterator
This can be substituted by a reflect value iterator that goes over a
value with a zero-sized array.
* Add a simple iterator that implements label iterator
In the long run this will completely replace the LabelIterator
interface.
* Replace reflect value iterator with simple iterator
* Pass label storage to new export labels, not label iterator
* Drop label iterator interface, rename storage iterator to label iterator
* Drop clone operation from iterator
It's a leftover from interface times and now it's pointless - the
iterator is a simple struct, so cloning it is a simple copy.
* Drop Reset from label iterator
The sole existence of Reset was actually for benchmarking convenience.
Now we can just copy the iterator cheaply, so a need for Reset is no
more.
* Drop noop iterator tests
* Move back iterator tests to export package
* Eagerly get the reflect value of ordered labels
So we won't get into problems when several goroutines want to iterate
the same labels at the same time. Not sure if this would be a big
deal, since every goroutine would compute the same reflect.Value, but
concurrent write to the same memory is bad anyway. And it doesn't cost
us any extra allocations anyway.
* Replace NewSliceLabelIterator() with a method of LabelSlice
* Add some documentation
* Documentation fixes
2020-03-20 00:01:34 +02:00
|
|
|
return at.Interface()
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
// labsFor sanitizes the input LabelSet. The input will be rejected
|
|
|
|
// if it was created by another Meter instance, for example.
|
|
|
|
func (m *SDK) labsFor(ls api.LabelSet) *labels {
|
2019-12-24 09:03:04 +02:00
|
|
|
if del, ok := ls.(api.LabelSetDelegate); ok {
|
|
|
|
ls = del.Delegate()
|
|
|
|
}
|
2019-10-29 22:27:22 +02:00
|
|
|
if l, _ := ls.(*labels); l != nil && l.meter == m {
|
|
|
|
return l
|
|
|
|
}
|
|
|
|
return &m.empty
|
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (m *SDK) NewSyncInstrument(descriptor api.Descriptor) (api.SyncImpl, error) {
|
|
|
|
return &syncInstrument{
|
|
|
|
instrument: instrument{
|
|
|
|
descriptor: descriptor,
|
|
|
|
meter: m,
|
|
|
|
},
|
2020-03-11 20:57:57 +02:00
|
|
|
}, nil
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (m *SDK) NewAsyncInstrument(descriptor api.Descriptor, callback func(func(core.Number, api.LabelSet))) (api.AsyncImpl, error) {
|
|
|
|
a := &asyncInstrument{
|
|
|
|
instrument: instrument{
|
|
|
|
descriptor: descriptor,
|
|
|
|
meter: m,
|
|
|
|
},
|
|
|
|
callback: callback,
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
2020-03-19 21:02:46 +02:00
|
|
|
m.asyncInstruments.Store(a, nil)
|
|
|
|
return a, nil
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
// Collect traverses the list of active records and observers and
|
|
|
|
// exports data for each active instrument. Collect() may not be
|
|
|
|
// called concurrently.
|
2019-10-29 22:27:22 +02:00
|
|
|
//
|
2019-11-05 23:08:55 +02:00
|
|
|
// During the collection pass, the export.Batcher will receive
|
2019-10-29 22:27:22 +02:00
|
|
|
// one Export() call per current aggregation.
|
2019-11-15 23:01:20 +02:00
|
|
|
//
|
|
|
|
// Returns the number of records that were checkpointed.
|
|
|
|
func (m *SDK) Collect(ctx context.Context) int {
|
2019-10-29 22:27:22 +02:00
|
|
|
m.collectLock.Lock()
|
|
|
|
defer m.collectLock.Unlock()
|
|
|
|
|
2020-03-05 22:15:30 +02:00
|
|
|
checkpointed := m.collectRecords(ctx)
|
2020-03-19 21:02:46 +02:00
|
|
|
checkpointed += m.collectAsync(ctx)
|
2020-03-05 22:15:30 +02:00
|
|
|
m.currentEpoch++
|
|
|
|
return checkpointed
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *SDK) collectRecords(ctx context.Context) int {
|
2019-11-15 23:01:20 +02:00
|
|
|
checkpointed := 0
|
|
|
|
|
2020-02-07 00:45:56 +02:00
|
|
|
m.current.Range(func(key interface{}, value interface{}) bool {
|
|
|
|
inuse := value.(*record)
|
|
|
|
unmapped := inuse.refMapped.tryUnmap()
|
|
|
|
// If able to unmap then remove the record from the current Map.
|
|
|
|
if unmapped {
|
|
|
|
m.current.Delete(inuse.mapkey())
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
2020-02-07 00:45:56 +02:00
|
|
|
// Always report the values if a reference to the Record is active,
|
|
|
|
// this is to keep the previous behavior.
|
|
|
|
// TODO: Reconsider this logic.
|
|
|
|
if inuse.refMapped.inUse() || atomic.LoadInt64(&inuse.modified) != 0 {
|
|
|
|
atomic.StoreInt64(&inuse.modified, 0)
|
2020-03-05 22:15:30 +02:00
|
|
|
checkpointed += m.checkpointRecord(ctx, inuse)
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
2020-02-07 00:45:56 +02:00
|
|
|
// Always continue to iterate over the entire map.
|
|
|
|
return true
|
|
|
|
})
|
2019-10-29 22:27:22 +02:00
|
|
|
|
2019-11-15 23:01:20 +02:00
|
|
|
return checkpointed
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (m *SDK) collectAsync(ctx context.Context) int {
|
2020-03-05 22:15:30 +02:00
|
|
|
checkpointed := 0
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
m.asyncInstruments.Range(func(key, value interface{}) bool {
|
|
|
|
a := key.(*asyncInstrument)
|
|
|
|
a.callback(a.observe)
|
|
|
|
checkpointed += m.checkpointAsync(ctx, a)
|
2020-03-05 22:15:30 +02:00
|
|
|
return true
|
|
|
|
})
|
|
|
|
|
|
|
|
return checkpointed
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *SDK) checkpointRecord(ctx context.Context, r *record) int {
|
2020-03-19 21:02:46 +02:00
|
|
|
return m.checkpoint(ctx, &r.inst.descriptor, r.recorder, r.labels)
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (m *SDK) checkpointAsync(ctx context.Context, a *asyncInstrument) int {
|
|
|
|
if len(a.recorders) == 0 {
|
2019-11-15 23:01:20 +02:00
|
|
|
return 0
|
|
|
|
}
|
2020-03-05 22:15:30 +02:00
|
|
|
checkpointed := 0
|
2020-03-19 21:02:46 +02:00
|
|
|
for encodedLabels, lrec := range a.recorders {
|
2020-03-05 22:15:30 +02:00
|
|
|
epochDiff := m.currentEpoch - lrec.modifiedEpoch
|
|
|
|
if epochDiff == 0 {
|
2020-03-19 21:02:46 +02:00
|
|
|
checkpointed += m.checkpoint(ctx, &a.descriptor, lrec.recorder, lrec.labels)
|
2020-03-05 22:15:30 +02:00
|
|
|
} else if epochDiff > 1 {
|
|
|
|
// This is second collection cycle with no
|
|
|
|
// observations for this labelset. Remove the
|
|
|
|
// recorder.
|
2020-03-19 21:02:46 +02:00
|
|
|
delete(a.recorders, encodedLabels)
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
|
|
|
}
|
2020-03-19 21:02:46 +02:00
|
|
|
if len(a.recorders) == 0 {
|
|
|
|
a.recorders = nil
|
2020-03-05 22:15:30 +02:00
|
|
|
}
|
|
|
|
return checkpointed
|
|
|
|
}
|
2019-11-15 23:01:20 +02:00
|
|
|
|
2020-03-19 21:02:46 +02:00
|
|
|
func (m *SDK) checkpoint(ctx context.Context, descriptor *metric.Descriptor, recorder export.Aggregator, labels *labels) int {
|
2020-03-05 22:15:30 +02:00
|
|
|
if recorder == nil {
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
recorder.Checkpoint(ctx, descriptor)
|
2020-03-11 18:11:27 +02:00
|
|
|
|
2020-03-20 18:17:45 +02:00
|
|
|
labels.ensureEncoded(m.labelEncoder)
|
|
|
|
exportLabels := export.NewLabels(labels, labels.cachedEncoded, m.labelEncoder)
|
2020-03-05 22:15:30 +02:00
|
|
|
exportRecord := export.NewRecord(descriptor, exportLabels, recorder)
|
|
|
|
err := m.batcher.Process(ctx, exportRecord)
|
2019-11-15 23:01:20 +02:00
|
|
|
if err != nil {
|
|
|
|
m.errorHandler(err)
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
2019-11-15 23:01:20 +02:00
|
|
|
return 1
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
2020-03-20 17:58:32 +02:00
|
|
|
// Resource returns the Resource this SDK was created with describing the
|
|
|
|
// entity for which it creates instruments for.
|
|
|
|
//
|
|
|
|
// Resource means that the SDK implements the Resourcer interface and
|
|
|
|
// therefore all metric instruments it creates will inherit its
|
|
|
|
// Resource by default unless explicitly overwritten.
|
|
|
|
func (m *SDK) Resource() resource.Resource {
|
|
|
|
return m.resource
|
|
|
|
}
|
|
|
|
|
2019-10-29 22:27:22 +02:00
|
|
|
// RecordBatch enters a batch of metric events.
|
|
|
|
func (m *SDK) RecordBatch(ctx context.Context, ls api.LabelSet, measurements ...api.Measurement) {
|
|
|
|
for _, meas := range measurements {
|
2020-03-19 21:02:46 +02:00
|
|
|
meas.SyncImpl().RecordOne(ctx, meas.Number(), ls)
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
func (r *record) RecordOne(ctx context.Context, number core.Number) {
|
2019-11-15 23:01:20 +02:00
|
|
|
if r.recorder == nil {
|
|
|
|
// The instrument is disabled according to the AggregationSelector.
|
|
|
|
return
|
|
|
|
}
|
2020-03-19 21:02:46 +02:00
|
|
|
if err := aggregator.RangeTest(number, &r.inst.descriptor); err != nil {
|
2019-11-15 23:01:20 +02:00
|
|
|
r.labels.meter.errorHandler(err)
|
|
|
|
return
|
|
|
|
}
|
2020-03-19 21:02:46 +02:00
|
|
|
if err := r.recorder.Update(ctx, number, &r.inst.descriptor); err != nil {
|
2019-11-15 23:01:20 +02:00
|
|
|
r.labels.meter.errorHandler(err)
|
|
|
|
return
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-12-28 02:30:19 +02:00
|
|
|
func (r *record) Unbind() {
|
2020-02-07 00:45:56 +02:00
|
|
|
// Record was modified, inform the Collect() that things need to be collected.
|
|
|
|
// TODO: Reconsider if we should marked as modified when an Update happens and
|
|
|
|
// collect only when updates happened even for Bounds.
|
|
|
|
atomic.StoreInt64(&r.modified, 1)
|
|
|
|
r.refMapped.unref()
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
func (r *record) mapkey() mapkey {
|
|
|
|
return mapkey{
|
2020-03-19 21:02:46 +02:00
|
|
|
descriptor: &r.inst.descriptor,
|
2020-03-11 18:11:27 +02:00
|
|
|
ordered: r.labels.ordered,
|
2019-10-29 22:27:22 +02:00
|
|
|
}
|
|
|
|
}
|