You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2018/05/30 17:33: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=16495474#comment-16495474 ]
Luke Cwik commented on BEAM-4430:
---------------------------------
What about documenting what runners need to do to integrate with the perfkit framework as the guide is written with users and IO authors in mind.
> 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
>
> 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)