[
https://issues.apache.org/jira/browse/FLINK-19654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214571#comment-17214571
]
Huang Xingbo commented on FLINK-19654:
--------------------------------------
[~dian.fu] Thanks a lot for opening this ticket. [~rmetzger] Thanks a lot for
the suggestions.
1. I very much agree to put the test of pyflink datastream and table together,
which can save the time of compiling/installing the sdist package and the time
of starting and stopping the cluster.
2. pyflink on yarn test
I think we can't remove this test which will cover some pyflink special
features of on yarn. But I will optimize this test to remove the part of
downloading dependency, which is the main reason for the slow test.
3. I will change the third party req package of `scipy` to other small package.
The `scipy` package is about 25MB. I think this is the main reason for the slow
test.
> 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
> 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)
