Skip to content

Add near-max listpack ZINCRBY coverage (1M keys × 120 members × 50B)#417

Open
fcostaoliveira wants to merge 1 commit into
mainfrom
add-zincrby-nearmax-listpack-coverage
Open

Add near-max listpack ZINCRBY coverage (1M keys × 120 members × 50B)#417
fcostaoliveira wants to merge 1 commit into
mainfrom
add-zincrby-nearmax-listpack-coverage

Conversation

@fcostaoliveira

@fcostaoliveira fcostaoliveira commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator

Adds a ZINCRBY benchmark for sorted sets at near-max listpack size — 1,000,000 keys, each with 120 members of 50-byte strings (just below zset-max-listpack-entries 128 and zset-max-listpack-value 64). ZINCRBY repeatedly increments one fixed member, forcing an almost-full listpack traversal on every call.

The existing 16-element listpack ZINCRBY spec is too small to exercise this path. This near-max variant closes a coverage gap relevant to redis/redis#15288.

Validated with redis-benchmarks-spec-cli --tool stats --fail-on-required-diff (passes).


Note

Cursor Bugbot is generating a summary for commit c1c3bf0. Configure here.

The existing 16-element listpack ZINCRBY spec is too small to exercise the
near-max-listpack lpFind/traversal path (120 members, just below
zset-max-listpack-entries 128). Adds coverage for the regime reported in
redis/redis#15288.
@jit-ci

jit-ci Bot commented Jun 10, 2026

Copy link
Copy Markdown

🛡️ Jit Security Scan Results

CRITICAL HIGH MEDIUM

✅ No security findings were detected in this PR


Security scan by Jit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant