NOTE
Netty Direct / Off-Heap Memory
Why Netty uses direct buffers, their I/O advantages and native-memory/reference-counting risks.
This is a historical learning note and may contain outdated or incomplete understanding.
Direct buffers place backing bytes outside the ordinary Java heap, which can reduce copying between heap arrays and native I/O in some paths and works well with pooled networking workloads.
They are not “free memory”: direct/native allocations count toward process/container memory and can cause native/direct-memory exhaustion even when Java heap looks healthy.
Netty’s pooled/reference-counted model means timely logical release is essential. Monitor RSS/native memory and allocator metrics together with heap/GC data.