You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Łukasz Gajowy (JIRA)" <ji...@apache.org> on 2018/06/08 16:08:00 UTC

[jira] [Commented] (BEAM-4430) Improve Performance Testing Documentation

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

Łukasz Gajowy commented on BEAM-4430:
-------------------------------------

[~lcwik] (sorry, I missed your comment before) 

I recently started to gather issues related to this topic on JIRA, see BEAM-4464 and BEAM-4465 Maybe it's a good idea to just mention them in the docs? Do you think [https://beam.apache.org/documentation/io/testing/#i-o-transform-integration-tests] is a good place for this, or maybe this should be somewhere else?

> Improve Performance Testing Documentation
> -----------------------------------------
>
>                 Key: BEAM-4430
>                 URL: https://issues.apache.org/jira/browse/BEAM-4430
>             Project: Beam
>          Issue Type: Wish
>          Components: testing
>            Reporter: Łukasz Gajowy
>            Assignee: Łukasz Gajowy
>            Priority: Critical
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, the only documentation regarding IO Performance Testing can be found here: [https://beam.apache.org/documentation/io/testing/#i-o-transform-integration-tests]. This is certainly not enough given that the performance testing framework currently allows to run tests:
>  - on local or hdfs filesystems
>  - on direct or dataflow runners
>  - manually using integrationTest task
>  - automatically using performanceTest task
>  - using pkb.py tool directly (PerfKitBenchmarker)
>  - on demand from pending Pull Requests 
>  - detecting anomalies
>  - gathering results in dashboards
> All the above bullets (and maybe others - to be investigated) need more explanation in the docs to make the Performance Testing Framework usable by the broader community.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)