Maksim Kviatkouski commented on OAK-6209:

Just realized I have a question about approached you proposed to deal with 
output. If I create dummy {{OutputStream}} that discards all the output I still 
need a way to output essential information like stats. What do you think is the 
best way to deal with it? I can think of two solutions:
- Since "must have" output is printed in a very limited number of cases I can 
refactor it to make call like ((FilteringPrintStream) 
System.out.println)(formattedStatsObj, true) assuming that FilteringPrintStream 
will not discard that output due to flag passed.
- Somehow make BenchmarkOutputStrategy to set system output back to regular 
output and change it back to what it was after it's done working. I don't like 
this approach though since it changes state of a globally available object 
which is not really easy to deal with later.
Please let me know if you have more elegant solution.

> The benchmark runner should produce machine-friendly output
> -----------------------------------------------------------
>                 Key: OAK-6209
>                 URL: https://issues.apache.org/jira/browse/OAK-6209
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: benchmarks
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>            Priority: Major
>         Attachments: oak-6209.patch, sample-machine-readable-output.txt
> The benchmark runner currently produce output in the following format.
> {noformat}
> Apache Jackrabbit Oak 1.8-SNAPSHOT
> # LoginTest                        C     min     10%     50%     90%     max  
>      N 
> Oak-Segment-Tar                    1     472     494     522     552     631  
>    115
> # LoginLogoutTest                  C     min     10%     50%     90%     max  
>      N 
> Oak-Segment-Tar                    1     472     479     513     543     568  
>    118
> {noformat}
> While this format is well formatted and easy to read, it's a pain to process 
> with standard command line utilities. The benchmark runner should give the 
> possibility to produce machine-friendly output, like the following.
> {noformat}
> LoginTest,Oak-Segment-Tar,1,472,494,522,552,631,115
> LoginLogoutTest,Oak-Segment-Tar,1,472,479,513,543,568,118
> {noformat}

This message was sent by Atlassian JIRA

Reply via email to