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 <hoangthevinh....@gmail.com> 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. >
