Module memory 

Custom allocators tuned for graph database workloads.

These allocators give you better performance than the global allocator for specific patterns. Pick the right one for your use case:

Allocator	Best for	Trade-off
arena	MVCC versioning, bulk alloc/dealloc	Can’t free individual items
bump	Temporary data within a query	Must reset to free anything
pool	Frequently reused objects	Fixed-size objects only
buffer	Large data, memory pressure	More complex API

Re-exports

pub use arena::AllocError;

pub use arena::Arena;

pub use arena::ArenaAllocator;

pub use buffer::BufferManager;

pub use buffer::BufferManagerConfig;

pub use buffer::BufferStats;

pub use buffer::MemoryConsumer;

pub use buffer::MemoryGrant;

pub use buffer::MemoryRegion;

pub use buffer::PressureLevel;

pub use bump::BumpAllocator;

pub use pool::ObjectPool;

pub use reporter::MemoryReporter;

pub use usage::IndexMemory;

pub use usage::MvccMemory;

pub use usage::NamedMemory;

pub use usage::StoreMemory;

pub use usage::StringPoolMemory;

Modules

arena

Epoch-based arena allocator for MVCC.

buffer

Centralized memory management with pressure handling.

bump

Bump allocator for temporary allocations.

pool

Object pool for reusing frequently allocated types.

reporter

Memory introspection trait for reporting heap usage.

usage

Memory usage breakdown types for graph store components.