Add Memory Usage Calculation for eStore Data Structure#2
Open
sggeorgiev wants to merge 1 commit intomoticless:redesign-expirefrom
Open
Add Memory Usage Calculation for eStore Data Structure#2sggeorgiev wants to merge 1 commit intomoticless:redesign-expirefrom
sggeorgiev wants to merge 1 commit intomoticless:redesign-expirefrom
Conversation
moticless
pushed a commit
that referenced
this pull request
Mar 12, 2026
…#14845) ## Problem PR redis#14787 introduced **Tcl 9 support for the test suite**, but it still fails on my machine (**macOS 26.3, Tcl 9.0.3**). Some tests fail and the runner may hang. Example: ```bash $ tclsh <<<'puts $tcl_version' 9.0.3 $ make test [err]: BITCOUNT against test vector #2 Expected [r bitcount str] == 4 ``` This is caused by **behavior changes in Tcl 9**, including: - `string length` returning **character count** instead of **byte count** - binary sockets rejecting characters with code points **>255** - differences in `string is wideinteger` Parts of the Redis Tcl test framework rely on **byte-oriented behavior**, which breaks under Tcl 9. ## Changes ### 1. Fix IPC payload encoding in test runner `tests/unit/memefficiency.tcl` contains a **non-ASCII quote character**: https://github.com/redis/redis/blob/fe16003e667407973296ae11b039baa2f9d088c2/tests/unit/memefficiency.tcl#L826 Under Tcl 9 this can corrupt the IPC stream when the test runner serializes Tcl code blocks, causing the runner to hang. Instead of fixing only this character, the IPC payload is now explicitly encoded using: ```tcl encoding convertto utf-8 ``` This makes the protocol robust against future non-ASCII characters. ### 2. Avoid Tcl 9 glob backtracking issue Replaced: ```tcl string match "*[^\u0000-\u00ff]*" $a ``` with: ```tcl regexp {[^\u0000-\u00ff]} $a ``` This avoids a **catastrophic backtracking issue in Tcl 9's glob matcher** while preserving the same behavior. ### 3. Update DIGEST validation The previous check relied on:`string is wideinteger` which behaves differently in Tcl 9. The assertion now validates the **expected DIGEST format directly**.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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