Skip to content

[pull] memtable_as_log_index from topling:memtable_as_log_index - #23

Merged
pull[bot] merged 6 commits into
hugegraph:memtable_as_log_indexfrom
topling:memtable_as_log_index
Aug 2, 2026
Merged

[pull] memtable_as_log_index from topling:memtable_as_log_index#23
pull[bot] merged 6 commits into
hugegraph:memtable_as_log_indexfrom
topling:memtable_as_log_index

Conversation

@pull

@pull pull Bot commented Aug 2, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

rockeet added 6 commits August 2, 2026 22:50
Avoid snprintf+open on each /proc/<pid>/fd entry; keep one O_DIRECTORY
handle for readdir and openat during the per-second pagecache scan.
Apply at runtime via graft_bench_yaml so rockside yaml stays at 2;
verify base and dictzip10-out copies include the grafted multiplier.
Apply at runtime via graft_bench_yaml; verify base and dictzip10-out copies.
After level0 slowdown and multiplier tweaks, revert base SST size to match
rockside defaults and reduce /dev/shm pressure from excess L0 files.
Replace dispatch level_writers with simple through L2, light_zip for L3-L5,
and zip at L6 to reduce L0 pressure while keeping deeper levels compressed.
Note that cached reads avoid disk I/O and let the DB benefit in its own way.
@pull pull Bot locked and limited conversation to collaborators Aug 2, 2026
@pull pull Bot added the ⤵️ pull label Aug 2, 2026
@pull
pull Bot merged commit d226e9e into hugegraph:memtable_as_log_index Aug 2, 2026
1 check failed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant