You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Piotr Nowojski (JIRA)" <ji...@apache.org> on 2018/10/18 12:18:00 UTC

[jira] [Resolved] (FLINK-10537) Network throughput performance regression after broadcast changes

     [ https://issues.apache.org/jira/browse/FLINK-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Nowojski resolved FLINK-10537.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.0

After merging the PR issues seems to be resolved.

Merged to master as 2c53a175228be3f1b840a45504cc69de18e84df8

> Network throughput performance regression after broadcast changes
> -----------------------------------------------------------------
>
>                 Key: FLINK-10537
>                 URL: https://issues.apache.org/jira/browse/FLINK-10537
>             Project: Flink
>          Issue Type: Bug
>          Components: Network
>    Affects Versions: 1.7.0
>            Reporter: Piotr Nowojski
>            Assignee: Piotr Nowojski
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.0
>
>
> There is a slight network throughput regression introduced in: https://issues.apache.org/jira/browse/FLINK-9913
> It is visible in the following benchmark:
> [http://codespeed.dak8s.net:8000/timeline/#/?exe=1&ben=networkThroughput.1,100ms&env=2&revs=200&equid=off&quarts=on&extr=on]
> (drop in the chart that happened since 21st September.)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)