You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/10/15 08:17:00 UTC

[jira] [Commented] (FLINK-19654) Improve the execution time of PyFlink end-to-end tests

    [ https://issues.apache.org/jira/browse/FLINK-19654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214506#comment-17214506 ] 

Robert Metzger commented on FLINK-19654:
----------------------------------------

Thanks for opening this ticket. I attached the source of your data to this ticket.

> 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)