[
https://issues.apache.org/jira/browse/BEAM-4430?focusedWorklogId=119380&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-119380
]
ASF GitHub Bot logged work on BEAM-4430:
----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jul/18 14:26
Start Date: 05/Jul/18 14:26
Worklog Time Spent: 10m
Work Description: lgajowy commented on issue #465: [BEAM-4430] Improve
Performance Testing Documentation
URL: https://github.com/apache/beam-site/pull/465#issuecomment-402740466
Ok, Thanks @szewi and thanks for the effort of testing this on Minikube.
Initially, there was a mention in the docs that it is best to use GKE as this
is what we've used for the testing infrastructure (and know it best). I deleted
it but now I think that it's good to leave such note in the docs.
Since @chamikaramj is unavailable it might be a good idea to add another
reviewer here. @iemejia, do you think you could take a look too?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 119380)
Time Spent: 2h 10m (was: 2h)
> Improve Performance Testing Documentation
> -----------------------------------------
>
> Key: BEAM-4430
> URL: https://issues.apache.org/jira/browse/BEAM-4430
> Project: Beam
> Issue Type: Wish
> Components: testing
> Reporter: Lukasz Gajowy
> Assignee: Lukasz Gajowy
> Priority: Critical
> Time Spent: 2h 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)
