## What is the purpose of the change Currently the `NetworkBufferPool` already uses off-heap memory directly. But the `BufferPool` for `SpilledSubpartitionView` still uses heap memory by default. It should keep the same behavior with `NetworkBufferPool` and it may get benefit for reusing this off-heap memory in netty stack during transporting.
## Brief change log - *Use off-heap memory directly for `SpillReadBufferPool` in `SpilledSubpartitionView`.* ## Verifying this change This change is already covered by existing tests, such as *SpillableSubpartitionTest*. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (yes) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (not applicable) [ Full content available at: https://github.com/apache/flink/pull/6762 ] This message was relayed via gitbox.apache.org for [email protected]
