[ https://issues.apache.org/jira/browse/AVRO-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved AVRO-2251. ------------------------------- Resolution: Fixed Fix Version/s: 1.9.0 Merged. Thanks! > 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)