Repository navigation
perf(deletion-vector): use zero-copy memoryview for deserialization - #4181
Open
ArslanAnjum wants to merge 1 commit into
Open
ArslanAnjum wants to merge 1 commit into
ArslanAnjum wants to merge 1 commit into
Conversation
Replace repeated byte string slicing with pointer offset tracking via Python's built-in memoryview. This avoids O(N^2) memory buffer allocations during parsing, improving throughput by up to 39x on large payload sizes.
ArslanAnjum
marked this pull request as ready for review
October 29, 2026 18:56
This branch has not been deployed
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
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.
perf: optimize deletion vector deserialization using zero-copy memoryview
Summary
Optimizes deletion vector parsing by replacing repeated byte string slicing (
pl = pl[4:]) with zero-copy pointer tracking via Python's built-inmemoryview.Repeatedly slicing$O(N^2)$ memory copying behavior as payload sizes grow. Utilizing $O(1)$ during parsing, improving execution times by up to ~39x on large dense payloads.
bytesobjects creates new allocations and copies remaining payload data into memory on every iteration, leading tomemoryviewkeeps memory allocations atBenchmark Results
Benchmarks were executed across four real-world Iceberg deletion vector scenarios using
pytest-benchmark(min_rounds=1000,warmup=True,disable_gc=True):small_sparsegaps_sparse_keysmedium_typicallarge_denseDetailed Terminal Benchmark Output
Reproducing Benchmarks
Run the benchmark script below using
pytest-benchmark: