feat(vortex-geo): geometry Bbox zone-map statistic + distance-filter pruning#8561
Open
HarukiMoriarty wants to merge 4 commits into
Open
feat(vortex-geo): geometry Bbox zone-map statistic + distance-filter pruning#8561HarukiMoriarty wants to merge 4 commits into
Bbox zone-map statistic + distance-filter pruning#8561HarukiMoriarty wants to merge 4 commits into
Conversation
Signed-off-by: Nemo Yu <zyu379@wisc.edu>
Merging this PR will improve performance by 10.99%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | Simulation | compact_sliced[(4096, 90)] |
866.7 ns | 779.2 ns | +11.23% |
| ⚡ | Simulation | compact_sliced[(16384, 90)] |
900.8 ns | 813.3 ns | +10.76% |
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing nemo/geo-bounds-zonemap (1928666) with develop (3493ecb)
Footnotes
-
4 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
The zoned writer serializes each zone stat descriptor to persist it, but GeometryBounds used the default (non-serializable), so writing a geometry column zone map failed at write time. Add serialize/deserialize (no options) plus a regression test. Signed-off-by: Nemo Yu <zyu379@wisc.edu>
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.
Summary
Adds spatial chunk-pruning to Vortex. A new
GeometryBoundsaggregate stores a per-chunk minimum bounding box (MBR) as a zone-map statistic, and a stats-rewrite rule uses it to skip chunks that cannot satisfy aST_Distance(geom, const) <= rfilter.Limitation
<=/<are pruned.>/>=are soundly prunable via the symmetric farthest-corner bound but are intentionally omitted (rarely?)Testing
8 new vortex-geo tests. Point bbox across batches; Polygon bbox over all ring vertices, empty group → null, and registry self-declaration. only <=/< prune while >/>=/==/!= don't (parameterized), distance symmetry, non-distance comparisons ignored, and an end-to-end falsify.