Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 543E3200BE7 for ; Tue, 20 Dec 2016 09:52:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 52CBE160B29; Tue, 20 Dec 2016 08:52:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9DE61160B1B for ; Tue, 20 Dec 2016 09:51:59 +0100 (CET) Received: (qmail 52362 invoked by uid 500); 20 Dec 2016 08:51:58 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 52352 invoked by uid 99); 20 Dec 2016 08:51:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2016 08:51:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B6C732C03DC for ; Tue, 20 Dec 2016 08:51:58 +0000 (UTC) Date: Tue, 20 Dec 2016 08:51:58 +0000 (UTC) From: "godfrey he (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (FLINK-5342) Setting the parallelism automatically for operators base on cost model MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 20 Dec 2016 08:52:00 -0000 [ https://issues.apache.org/jira/browse/FLINK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762989#comment-15762989 ] godfrey he edited comment on FLINK-5342 at 12/20/16 8:51 AM: ------------------------------------------------------------- I think it's difficult and unintuitive about tuning the parallelism of all operators. User does not know the target operators translated from a query. And when more calcite rules added, the execution graph will be different with before for the same query. So as a first step, I think we can give coarse-grained control. After have statistics about the input and more correct cost of each operator, we can set the parallelism for each operator base on cost model. was (Author: godfreyhe): I think it's difficult and unintuitive about tuning the parallelism of all operators. User does not know the target operators translated from a query. When more calcite rules added, the execution graph will be different with before for the same query. So as a first step, I think we can give coarse-grained control. After we have statistics about the input and more correct cost of each operator, we can set the parallelism for each operator base on cost model. > Setting the parallelism automatically for operators base on cost model > ---------------------------------------------------------------------- > > Key: FLINK-5342 > URL: https://issues.apache.org/jira/browse/FLINK-5342 > Project: Flink > Issue Type: Improvement > Components: Table API & SQL > Reporter: godfrey he > > On Flink table API, a query will be translated to operators without parallelism. And user do not know even do not care the target operators translated from query. So it's better to set the parallelism automatically for each operator base on cost model. -- This message was sent by Atlassian JIRA (v6.3.4#6332)