fallintoplace opened a new pull request, #2272: URL: https://github.com/apache/iceberg-go/pull/2272
## What Cache positional-delete path bounds when building the partition index. ## Why Each data-file lookup reads the same delete-file path bounds again. ## Implementation - Store owned bounds and skip flags with each sorted entry. - Keep path-scoped deletes and conservative handling of missing bounds. - Add regression coverage and an in-package benchmark. ## Benchmark Isolated old/new path-pruning benchmark with 2,048 delete files and 512 data paths; Go 1.23.2, Linux/amd64, AMD EPYC 9V74, GOMAXPROCS=1; median of five 600 ms runs. | Metric | Before | After | Change | | --- | ---: | ---: | ---: | | Time | 64.2 us/op | 16.8 us/op | 3.82x faster | | Bytes | 0 B/op | 0 B/op | Same | | Allocations | 0 allocs/op | 0 allocs/op | Same | This measures path pruning only, not a full Iceberg scan. Reproduce the in-package benchmark with `go test ./table -run '^$' -bench '^BenchmarkPositionalDeleteIndexPartitionPathBounds$' -benchmem`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
