Repository navigation
Conversation
A point read decompresses one block to serve one event of about 250 bytes, so a 32 KiB block made every cache miss decompress about 128 events to serve one. Measured on the events corpus at limit=1000, 8 KiB against 32 KiB: service p50 -53%, p99 -59% and peak RSS -41% at stress density (sac-6000); neutral at pubnet density; +0.8% disk; ingest unchanged. 4 KiB adds nothing further. This is the hot tier only. RocksDB reads any block size, so existing databases keep working and pick up the new size as compaction rewrites them. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QHnF5BhsuoxpWxGmatQzmt
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.
What
Sets the hot store's DataCF block size (
dataCFBlockSize) to 8 KiB, down from 32 KiB.Why
A point read decompresses one block to serve one event of about 250 bytes, so a 32 KiB block made every cache miss decompress about 128 events to serve one. Measured on the events corpus at limit=1000, 8 KiB against 32 KiB:
Split out of #968.
Known limitations
Hot tier only. RocksDB reads any block size, so existing databases keep working and pick up 8 KiB blocks as compaction rewrites them.
🤖 Generated with Claude Code