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 D6786200C5E for ; Sat, 22 Apr 2017 19:42:50 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D4F18160BA2; Sat, 22 Apr 2017 17:42:50 +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 276C8160B91 for ; Sat, 22 Apr 2017 19:42:50 +0200 (CEST) Received: (qmail 14997 invoked by uid 500); 22 Apr 2017 17:42:44 -0000 Mailing-List: contact dev-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 dev@flink.apache.org Received: (qmail 14985 invoked by uid 99); 22 Apr 2017 17:42:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Apr 2017 17:42:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 954EFC6AD8 for ; Sat, 22 Apr 2017 17:42:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id FiWhbLGZhvsI for ; Sat, 22 Apr 2017 17:42:41 +0000 (UTC) Received: from mail-qk0-f173.google.com (mail-qk0-f173.google.com [209.85.220.173]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C96CC5F245 for ; Sat, 22 Apr 2017 17:42:40 +0000 (UTC) Received: by mail-qk0-f173.google.com with SMTP id y63so62411151qkd.1 for ; Sat, 22 Apr 2017 10:42:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:date:message-id:subject:from:to; bh=pJyoAYuWhCBJnXqW8AG+5drYkPhVSftL8CHWMwDg8BQ=; b=ta6345G7le/fG/8GWRDoPj2ELG4gutEq2fRjgdzKHxusCGuYRQZnld9E+A+TlPAXJp OjtiUuSGzs+1iyCzguLMfO6mMUg7GRFyMkXpDZiQuwJfAIA4MnwQI6YgNfG7qcvIcaxa MlnkPfN0iGY+yGTUM1Szlr+loxvk6u7u1fDnt0u7iQR14AxtohdgSQ/305pl6XaEqxbh pLp2n08zm0heGSX65Vwl7g/SiWVK/uTTCVbJK7BFcpiUZeZj4JYe7h39crj2IKzp5lmc ZnfoU6WFpYVugu/5t7wvIK5NOQR03Ptcd+i/b2MkgJcp5H2eVbfaCo38GW6ekVVMFLOO ihtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=pJyoAYuWhCBJnXqW8AG+5drYkPhVSftL8CHWMwDg8BQ=; b=q+2P8IlWrG682Krj1DnnkudVoZp3D1vHXDgIzZdTwp8/PJUW0rPXa6KHepwWIBrIie RJMEwD7pLZifwjHFqJxs6DgTpttMtuvo8ycq2scTfopP8AS0n5RYwCPKQlel9JPFxcNM n9/tVEV1sORIX5j45jtzNch6JmLOEB5an4YFpz8EmIVeAMX/DXCBOgC1MSnJj+29x2/i 64aQ+r9SLG7V9KP3Zfm5LuB9NiBoFBga5UEY80MDDFTP1ivK86jo/PyJ73zoW80rPndA p1H+2IUcyevBFYcpQMJwtylRH1HFeAdMVlUXrDc/SKgOZqlxFfsIVkSnN9Bdus7DoXoz PDig== X-Gm-Message-State: AN3rC/41pP1wju2f9mdxddER+HN+KUhZyRfUWXUpKSPzBGpsKhFvmIgy l6kzQ7YTUmppwsdN5yQ= X-Received: by 10.55.107.132 with SMTP id g126mr17784318qkc.112.1492882953798; Sat, 22 Apr 2017 10:42:33 -0700 (PDT) Received: from localhost (ec2-54-158-21-32.compute-1.amazonaws.com. [54.158.21.32]) by smtp.gmail.com with ESMTPSA id y76sm8995831qka.51.2017.04.22.10.42.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Apr 2017 10:42:33 -0700 (PDT) Mime-Version: 1.0 Date: Sat, 22 Apr 2017 10:42:24 -0700 X-Mailer: Polymail Message-ID: <58fb95a40b92f30000c513dc@polymail.io> Subject: Resource overallocation From: "Luis Alves" To: "dev@flink.apache.org" Content-Type: multipart/alternative; boundary=622578c68218b2daac239fc2da9d97d61aed56468304a1c70b518318731f archived-at: Sat, 22 Apr 2017 17:42:51 -0000 --622578c68218b2daac239fc2da9d97d61aed56468304a1c70b518318731f Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Hi, Regarding the features on Flink that allow to optimize resource usage in th= e cluster (+ latency, throughput ...), i.e. slot sharing, task chaining, as= ync i/o and dynamic scaling, I would like to ask the following questions (a= ll in the stream processing context):=C2=A0 In which cases would someone be interested in having the number of slots in= a task manager higher than the number of cpu cores?=C2=A0 In which case should we prefer split a pipeline of tasks over multiple slot= s (disable slot sharing), instead of increasing the parallelism, in order f= or an application to keep up with the incoming data rates?=C2=A0 Is it possible that even when using all the features above, the resources r= eserved for a slot may be higher than the amount of resources that all the = tasks in the slot require, thus causing us to have resources that are reser= ved for a slot, but not being used? Is it possible that such problems appea= r when we have tasks in applications with different latencies (or different= parallelisms)? Or even when we are performing multiple aggregations (that = cannot be optimised using folds or reduces) on the same window?=C2=A0 Thanks in advance, Lu=C3=ADs Alves --622578c68218b2daac239fc2da9d97d61aed56468304a1c70b518318731f--