flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Derek VerLee <derekver...@gmail.com>
Subject Clarification on slots and efficiency
Date Wed, 11 Apr 2018 18:22:49 GMT
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <p>From the docs (
<a class="moz-txt-link-freetext" href="https://ci.apache.org/projects/flink/flink-docs-master/concepts/runtime.html">https://ci.apache.org/projects/flink/flink-docs-master/concepts/runtime.html</a>
      )<br>
    </p>
    <blockquote>
      <p>By adjusting the number of task slots, users can define how
        subtasks are isolated from each other. Having one slot per
        TaskManager means each task group runs in a separate JVM (which
        can be started in a
        separate container, for example). Having multiple slots
        means more subtasks share the same JVM. Tasks in the same JVM
        share TCP connections (via multiplexing) and
        heartbeat messages. They may also share data sets and data
        structures, thus reducing the per-task overhead.</p>
    </blockquote>
    <p>Does this mean that if the same task and job is running in two
      slots on the same task-manager, that messages that happen to move
      between these slots will do so more efficiently, and avoid
      serialization overhead?<br>
    </p>
    <p><br>
    </p>
  </body>
</html>

Mime
View raw message