Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Fri, 26 Jun 2015 20:32:05 +0000 (UTC)
From: "Gyula Fora (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12840975.1435350689000.30425.1435350725199@Atlassian.JIRA>
In-Reply-To: <JIRA.12840975.1435350689000@Atlassian.JIRA>
References: <JIRA.12840975.1435350689000@Atlassian.JIRA>
 <JIRA.12840975.1435350689929@arcas>
Subject: [jira] [Created] (FLINK-2281) Allow chaining of operators with
 multiple inputs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Gyula Fora created FLINK-2281:
---------------------------------

             Summary: Allow chaining of operators with multiple inputs
                 Key: FLINK-2281
                 URL: https://issues.apache.org/jira/browse/FLINK-2281
             Project: Flink
          Issue Type: Improvement
          Components: Streaming
            Reporter: Gyula Fora
            Assignee: Gyula Fora
            Priority: Minor


Currently only operators with one input can be chained for better performance. In principle there is no reason why this should not be extended to multiple input operators (where chaining is applicable, i.e forward connected), to allow maximal speedup.

The concern usually arises that it might not be good to always chain everything in case of computation heavy operators. In these cases (if the job is otherwise viable) chaining only increases latency for some operations while the throughput is increased exploiting by increasing the parallelism to the freed resources.

In any case chaining should still remain tunable on an operator level.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)