Ability to add "jvm arguments" based on "@Param"

[Trask Stalnaker]

+1!, this would be very nice to have merged report across different JVM args

Trask
On Wed, May 27, 2015 at 4:10 PM Vladimir Sitnikov <
sitnikov.vladimir at gmail.com> wrote:

> Hi,
>
> It looks like it is a bit hard to benchmark cases when they require
> different values of jmv arguments.
>
> For instance, if you want to compare benchmarks that differ only in
> values of -D properties, then you can't have the overall report that
> includes both cases.
>
> In other words, you would have a couple of different result tables,
> while it would be nice to have a single summary one with a small tiny
> column that tells what was the parameter.
>
>
> I did not yet dig into the details how that could be implemented.
>
>
> It looks like the following might fly: add
> "OptionsBuilder.preProcessor(Consumer<OptionsBuilder> preprocessor)".
> For each benchmark method, jmh would create a child OptionsBuilder and
> call preprocessor on it, so each method could have a bit different
> arguments.
>
> We might even combine that with "skip this combination" feature. In
> other words, allow that "options preprocessor" to veto execution with
> given combinations of parameters.
>
>
>
> Please, please tell me I am overengineering and jmh can use @params
> for stuffing jvmArgs already.
>
> --
> Regards,
> Vladimir Sitnikov
>