jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francesco Mari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-6209) The benchmark runner should produce machine-friendly output
Date Tue, 03 Apr 2018 08:29:00 GMT

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

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

[~maksim_kviatkouski], thanks for contributing on this issue! I see two strategies to solve
this problem. 

# As you mentioned, you can suppress the unwanted output. The tests should be fixed to provide
additional output through a {{Logger}}. The output can be examined separately, if needed.
# You can include additional test outputs on their own lines, prefixed with a marker (for
example, {{#}}), so that a program processing the output can filter out those lines. 

I would like to assign this issue to you, to avoid duplicate effort. Is it fine for you?

> 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
>            Priority: Major
>
> 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)

Mime
View raw message