[
https://issues.apache.org/jira/browse/FLINK-19654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214589#comment-17214589
]
Robert Metzger commented on FLINK-19654:
----------------------------------------
Thanks. I assigned you to the ticket.
Can you do 1. 2. and 3. in separate pull requests, so that we quickly get the
time savings?
2. Can't we run the python tests with the regular YARN tests, where we are have
a cluster running already? (flink-yarn-tests)
Currently, the pyflink on yarn test is using a secured yarn cluster on docker,
which is extremely slow to set up and launch.
> Improve the execution time of PyFlink end-to-end tests
> ------------------------------------------------------
>
> Key: FLINK-19654
> URL: https://issues.apache.org/jira/browse/FLINK-19654
> Project: Flink
> Issue Type: Bug
> Components: API / Python, Tests
> Affects Versions: 1.12.0
> Reporter: Dian Fu
> Assignee: Huang Xingbo
> Priority: Major
> Attachments: image (7).png
>
>
> Thanks for the sharing from [~rmetzger], currently the test duration for
> PyFlink end-to-end test is as following:
> ||test case||average execution-time||maximum execution-time||
> |PyFlink Table end-to-end test|1340s|1877s|
> |PyFlink DataStream end-to-end test|387s|575s|
> |Kubernetes PyFlink application test|606s|694s|
> We need to investigate how to improve them to reduce the execution time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
