[ 
https://issues.apache.org/jira/browse/OAK-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16430318#comment-16430318
 ] 

Francesco Mari commented on OAK-6209:
-------------------------------------

[~maksim_kviatkouski], I think you reached a very good state with your efforts. 
I guess the time is right to propose a patch with what you have, and tackle the 
rest in follow-up issues. In particular, the following topics are good 
candidates for new issues:
 * review and adapt the benchmarks in order to produce unobtrusive debugging 
output;
 * design and implement a solution for printing the observation stats.

We don't need to solve everything with this issue. I think it's easier to 
follow the conversation if we keep the issues more focused.

Other than that, I find your idea of printing exception stack traces to stderr 
very good. Looking forward to a patch!

> 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: 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
(v7.6.3#76005)

Reply via email to