Setting AggregationPolicy for EVENTS AuxCounters

[Owen O'Malley]

In my case, I wanted to track another output attribute where the important
piece of information is how many times it happened in each trial rather
than a global count that depends on the total number of trials. For
example, with fork=10 and iterations=3, I end up post-processing to divide
by 30. JMH has the code to do average, it just doesn't provide an API to do
it.

.. Owen

On Mon, Nov 13, 2017 at 9:08 AM, Aleksey Shipilev <shade at redhat.com> wrote:

> On 10/27/2017 05:25 AM, Owen O'Malley wrote:
> > There doesn't seem to be any way to change the AggregationPolicy for
> > AuxCounters(EVENTS) so it is always sum. Did I miss something?
>
> Yes, that is by design: EVENTS are one-off things. If you want them to be
> treated as normal metrics,
> e.g. as invocation counts for @Benchmark methods, use OPERATIONS. Is there
> a compelling use case
> that does not fit either?
>
> -Aleksey
>
>