Raw data output
Petr Stefan
ptr.stef at gmail.com
Wed Jun 29 13:43:38 UTC 2016
Hi,
Dne 28.6.2016 v 15:16 Jens Wilke napsal(a):
> The reason why I choose single shot or through put, is because this results in the most accurate result
> for the type of operation I want to measure.
>
> How can I use your tools to some comparison? If it is fixed to sample mode I can't. But why this limitation?
>
> For example the ReadOnlyBenchmark yields 123378830 operations per seconds on latest hardware with four threads
> (with through put mode). For 30 seconds iterations time that would be 3701 million data points. It's a mental example, of course it couldn't be gathered with sample mode that way because it would heavily skew the result. But if it would work, why I should want to analyze the runtime of each operation?
>
> To be honest, the sample mode is the only mode I wonder how it can ever be of any use. That's
> why I am confused about the fact that you say it's the only useful one.
>
no, it's not JUST the sample time mode, it's all INCLUDING sample time
mode. This mode doesn't give us actual raw data while others modes do,
so we're only extending the output. Main goal is that for custom
processing we want to have raw data, not already preprocessed ones (as
sample time mode sort of behaves now).
Our tool is not ready yet for you, I'm currently developing it (which
includes also extending JMH).
Cheers,
P.S.
More information about the jmh-dev
mailing list