lements, exponentially
>>>>>>>> decaying
>>>>>>>> > sampling, which favours more recent elements, sliding window or
>>>>>>>> buckets.
>>>>>>>> >
>>>>>>>> > The que
indow or
>>>>>>> buckets.
>>>>>>> >
>>>>>>> > The question is now whether such an implementation already covers
>>>>>>> most use
>>>>>>> > cases or whether histograms should support more functio
wrote:
>>>>>> >
>>>>>> > > I think it is totally fine to add a "ThreadsafeCounter" that uses
>>>>>> an
>>>>>> > atomic
>>>>>> > > long internally
>>>>
t;>>> > > > configuring each Finagle source to use a single thread. We'll
>>>> > investigate
>>>> > > > the performance implications this week and update you with the
>>>> results.
>>>> > > >
>>>> > &g
t;
>>>>> > > I think it is totally fine to add a "ThreadsafeCounter" that uses
>>>>> an
>>>>> > atomic
>>>>> > > long internally
>>>>> > >
>>>>> > > On Sat, Jun 11, 2016 at 7
> > >> That being said, if adding threadsafe versions
of the Flink counters
> is
> > >> not an option, we'd also be fine with directly
reading and writing
> from
>
>>> > > >
>>> > > > On Friday, June 10, 2016, Steve Cosenza
>>> wrote:
>>> > > >
>>> > > >> +Chris Hogue who is also working on operationalizing Flink with me
>>> > > >&
> > >> not an option, we'd also be fine with directly
reading and writing
> from
> > the
> > >> singleton Codahale MetricsRegistry that you start
up in each
> > TaskManager.
>> Thanks for the background on your current implementations!
>> > > >>
>> > > >> While we don't require a specific implementation for histogram,
>> > counter,
>> > > >> or gauge, it just became clear that we'll need threadsa
gt; > > >> three of these metrics. This is because our messaging source is
> > > implemented
> > > >> using Finagle, and Finagle expects to be able to emit stats
> > concurrently
> > > >> from its managed threads.
> > > >>
&g
t; three of these metrics. This is because our messaging source is
> > implemented
> > >> using Finagle, and Finagle expects to be able to emit stats
> concurrently
> > >> from its managed threads.
> > >>
> > >> That being said, if adding thr
agle, and Finagle expects to be able to emit stats concurrently
> >> from its managed threads.
> >>
> >> That being said, if adding threadsafe versions of the Flink counters is
> >> not an option, we'd also be fine with directly reading and writing from
>
e with directly reading and writing from the
>> singleton Codahale MetricsRegistry that you start up in each TaskManager.
>>
>> Thanks,
>> Steve
>>
>> On Fri, Jun 10, 2016 at 7:10 AM, Stephan Ewen wrote:
>>
>>> A recent discussion brought up the point of
ot an option, we'd also be fine with directly reading and writing from the
> singleton Codahale MetricsRegistry that you start up in each TaskManager.
>
> Thanks,
> Steve
>
> On Fri, Jun 10, 2016 at 7:10 AM, Stephan Ewen > wrote:
>
>> A recent discussion brought up t
tly reading and writing from the
singleton Codahale MetricsRegistry that you start up in each TaskManager.
Thanks,
Steve
On Fri, Jun 10, 2016 at 7:10 AM, Stephan Ewen wrote:
> A recent discussion brought up the point of adding a "histogram" metric
> type to Flink. This open threa
A recent discussion brought up the point of adding a "histogram" metric
type to Flink. This open thread is to gather some more of the requirements
for that metric.
The most important question is whether users need Flink to offer specific
implementations of "Histogram",
16 matches
Mail list logo
