Memory Package

The Memory Package provides high-performance, zero-allocation memory management for network packet processing at 100M+ packets per second.

Why This Exists

Java's standard memory management creates garbage collection pressure that causes latency spikes in high-throughput scenarios. The Memory Package solves this with:

• Pre-allocated object pools

• View-based binding (no slice allocations)

• Slab memory allocation with automatic cleanup

• Lock-free concurrent access

Key Concepts

Memory Types

Two memory types for different scenarios:

Type	Segment	Use Case
FixedMemory	Permanently bound	Pool-allocated buffers
ScopedMemory	Rebindable	Zero-copy native capture

View Binding

Instead of creating slice objects, views share references:

// Direct binding - just 2 reference assignments
header.bind(packet.memory());

// The header's view points directly to packet's memory view
// When packet memory changes, header sees it immediately

Pool Infrastructure

Three pool types for different needs:

Pool	Purpose
FreeListPool	Generic objects, lock-free CAS
BucketPool	Variable-sized allocations
MemoryPool	FixedMemory with slab backing

Quick Example

// Create a bucketed packet pool
long[] sizes = {64, 1518, 9000, 65536};
BucketPool<Packet> pool = new BucketPool<>(settings, sizes, Packet::ofFixed);

// Allocate - finds smallest fitting bucket
Packet packet = pool.allocate(1500);  // → 1518-byte bucket

// Use
processPacket(packet);

// Recycle - returns to pool, no GC
packet.recycle();

Performance

Operation	Cost	Allocations
Direct bind	2 assignments	0
Pool allocate	CAS operation	0
Pool recycle	CAS operation	0

Next Steps

• Memory Types - FixedMemory vs ScopedMemory

• View Binding - Zero-allocation binding architecture

• Pool Infrastructure - Pool types and configuration

• Packet Pools - Complete packet pool examples