Return-Path: X-Original-To: apmail-flink-user-archive@minotaur.apache.org Delivered-To: apmail-flink-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AC72D17592 for ; Fri, 17 Jul 2015 07:14:29 +0000 (UTC) Received: (qmail 95234 invoked by uid 500); 17 Jul 2015 07:14:29 -0000 Delivered-To: apmail-flink-user-archive@flink.apache.org Received: (qmail 95160 invoked by uid 500); 17 Jul 2015 07:14:29 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flink.apache.org Delivered-To: mailing list user@flink.apache.org Received: (qmail 95150 invoked by uid 99); 17 Jul 2015 07:14:29 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jul 2015 07:14:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 0A67DC0710 for ; Fri, 17 Jul 2015 07:14:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.294 X-Spam-Level: **** X-Spam-Status: No, score=4.294 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 240Q7wfmujLE for ; Fri, 17 Jul 2015 07:14:22 +0000 (UTC) Received: from mail-vn0-f43.google.com (mail-vn0-f43.google.com [209.85.216.43]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 0A6BF2104E for ; Fri, 17 Jul 2015 07:14:22 +0000 (UTC) Received: by vnbf190 with SMTP id f190so10502047vnb.6 for ; Fri, 17 Jul 2015 00:14:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=hf1SkuoSua82pcWFQYD03OqGH6S/Uj8/6i/VgDv4vTE=; b=VMux0b/vKjjKJAGJDqMqRjl7flJMmUAZTDCnE1eC3ERL0JG6fQCpwlaOEbx/c32XGu Om79ee2bWXCar3Jl3G8UPvDOsSYG6UCwJE/iCNE74bzDBY9siEDNpCzad5umdj02twZP tQ9ikAW4WkyhE8wDmMDotESAbM8tPYtOohYRhca8+C5PHkd+jxRqeuib5gZH/o3Guvvp yEN7gEbEmhvJnuDD4t4CWDw/wNObGFYDSZA6ZXQei4kiZA8tLz/QuisMR4uFBU3JifBC 5TGqEb3yQyZG/Wzh8alDWwQLuZpfwKXwDS9skU2enEaIQ+WpS/ua0AFkQp4lg/usZdKD 4ahA== MIME-Version: 1.0 X-Received: by 10.52.179.73 with SMTP id de9mr15320105vdc.28.1437117261186; Fri, 17 Jul 2015 00:14:21 -0700 (PDT) Sender: ewenstephan@gmail.com Received: by 10.31.128.19 with HTTP; Fri, 17 Jul 2015 00:14:21 -0700 (PDT) In-Reply-To: <1437062028216-2106.post@n4.nabble.com> References: <1436996660691-2065.post@n4.nabble.com> <1437029688439-2074.post@n4.nabble.com> <1437048392897-2091.post@n4.nabble.com> <1437053664832-2095.post@n4.nabble.com> <1437062028216-2106.post@n4.nabble.com> Date: Fri, 17 Jul 2015 09:14:21 +0200 X-Google-Sender-Auth: 674s5O7gBtGy3l2KJsazuppE5UQ Message-ID: Subject: Re: Flink Scala performance From: Stephan Ewen To: user@flink.apache.org Content-Type: multipart/alternative; boundary=bcaec5171f5fda8b70051b0cefb4 --bcaec5171f5fda8b70051b0cefb4 Content-Type: text/plain; charset=UTF-8 The 349ms is how long it takes to run the job. The 18s is what it takes the command line client to submit the job. Like I said before, may be there are super long delays on your system when you spawn JVMs, or in your DNS resolution. Thay way, connecting to the cluster to submit the job will take a long time... On Thu, Jul 16, 2015 at 5:53 PM, Vinh June wrote: > I just checked on web job manager, it says that runtime for flink job is > 349ms, but actually it takes 18s using "time" command in terminal > Should I care more about the latter timing ? > > > > -- > View this message in context: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-Scala-performance-tp2065p2106.html > Sent from the Apache Flink User Mailing List archive. mailing list archive > at Nabble.com. > --bcaec5171f5fda8b70051b0cefb4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The=C2=A0349m= s is how long it takes to run the job. The 18s is what it takes the command= line client to submit the job.

Like I said before, may be there are super long delays on your system = when you spawn JVMs, or in your DNS resolution. Thay way, connecting to the= cluster to submit the job will take a long time...

On Thu, Jul 16, 2015 a= t 5:53 PM, Vinh June <hoangthevinh.htv@gmail.com> w= rote:
I just checked on web job manager, = it says that runtime for flink job is
349ms, but actually it takes 18s using "time" command in terminal=
Should I care more about the latter timing ?



--
View this message in context: http://apache-flink-user-mailing-list= -archive.2336050.n4.nabble.com/Flink-Scala-performance-tp2065p2106.html=
Sent from the Apache Flink User Mai= ling List archive. mailing list archive at Nabble.com.

--bcaec5171f5fda8b70051b0cefb4--