[
https://issues.apache.org/jira/browse/AVRO-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672705#comment-16672705
]
ASF GitHub Bot commented on AVRO-2251:
--------------------------------------
rstata opened a new pull request #365: AVRO-2251 part 2: Allow changes to COUNT
and CYCLES via system properties.
URL: https://github.com/apache/avro/pull/365
As I continue to work on performance testing, I'm wanting to experiment with
values for Perf.COUNT and Perf.CYCLES without having to recompile. This patch
allows for such experimentation.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Modify Perf.java to better support automation scripts
> -----------------------------------------------------
>
> Key: AVRO-2251
> URL: https://issues.apache.org/jira/browse/AVRO-2251
> Project: Avro
> Issue Type: Test
> Reporter: Raymie Stata
> Assignee: Raymie Stata
> Priority: Major
> Fix For: 1.9.0
>
>
> To better support automated performance-test suites, this patch proposes two
> new arguments to the 'Perf.java' command-line tool:
> The `-o' argument gives 'Perf.java' the name of a file that should get the
> results of the run. Currently, Perf.java sends output to System.out – but if
> 'Perf.java' is invoked using Maven, which is the easiest way to invoke it,
> then System.out is polluted with a bunch of other output. Redirecting
> 'Perf.java' output metrics to a file makes it easier for automation scripts
> to process those metrics.
> The `-c [spec]` argument tells 'Perf.java' to generate a comma-separated
> output. By default, all benchmark metrics are output, but the optional
> `spec` argument can be used to indicate exactly which metrics should be
> included in the CSV output. The default output of 'Perf.java' is optimized
> for human inspection – for example, it includes the text "ms" in the
> running-time column so humans will understand the units of the running-time
> metric. The `-c` option will tell 'Perf.java' to generate machine-optimized
> output that is easier to consume by automation scripts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
