Add Memory Usage Calculation for eStore Data Structure #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Introduces comprehensive memory usage tracking for ebuckets and estore data structures to enable better memory profiling and optimization.
Changes
ebMemUsage(): Calculates memory footprint of individual ebuckets instances
estoreMemUsage(): Calculates total memory usage across all buckets in an estore
Key Features
Stack Type: Recursively calculates L1/L2 levels plus L3 vector segments
Rax Type: Accounts for rax structure, nodes, keys, and segment headers
List Type: Returns 0 (items stored inline)
Empty Buckets: Fast-path returns 0
Cluster-aware: Optimized calculation for clustered vs non-clustered modes
Test Coverage
✅ Empty buckets return 0
✅ List-based buckets return 0 (inline storage)
✅ Rax-based buckets with multiple segments
✅ Extended segments with NextSegHdr
✅ Stack-based buckets with L1/L2/L3 levels
Use Cases
Memory profiling and debugging
Resource usage monitoring
Performance optimization analysis