On 23 Jun 2015, at 13:53, Stephan Ewen wrote:
> Currently, Flink does not cache anything across runs, except JAR files on the
> workers.
>
> The reason the first run is slower may be:
> - Because in the first run, code is distributed in the cluster. In
> subsequent runs, the JAR files need n
Currently, Flink does not cache anything across runs, except JAR files on
the workers.
The reason the first run is slower may be:
- Because in the first run, code is distributed in the cluster. In
subsequent runs, the JAR files need not be redistributed.
- Because the JIT takes a bit to kick in
hi flink community,
to time i test my flink app with a benchmark on an hadoop cluster (flink on
yarn).
my results show me that flink need for the first round more time as all
other rounds. maybe flink cache something in memory? and if i run the
benchmark 100 rounds my system freeze, i think the me
