[
https://issues.apache.org/jira/browse/FLINK-19654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dian Fu updated FLINK-19654:
----------------------------
Description:
Thanks for the sharing from [~rmetzger], currently the average 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.
was:
Currently the average 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.
> 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
>
> Thanks for the sharing from [~rmetzger], currently the average 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)
