Highlights
- Automated benchmark infrastructure
- Lays groundwork for storage and query optimizations in upcoming releases
- Numerous bugfixes
Gory Details
- Add public benchmark suite with MS MARCO and Wikipedia by @tjgreen42 in #66
- Fix excessive memory allocation in document scoring by @tjgreen42 in #68
- Run benchmarks on-demand and weekly (not on every PR) by @tjgreen42 in #69
- Pin Python to 3.10 for wikiextractor compatibility by @tjgreen42 in #70
- Add path filters to CI workflows by @tjgreen42 in #72
- Fix benchmark dataset labeling by @tjgreen42 in #71
- Fix JSON generation in extract_metrics.sh by @tjgreen42 in #73
- Run benchmark queries repeatedly for stable measurements by @tjgreen42 in #74
- Extract and publish metrics per-dataset when running all benchmarks by @tjgreen42 in #75
- Improve benchmark configuration and add index size tracking by @tjgreen42 in #76
- Improve benchmark dashboard: dataset sizes and compact layout by @tjgreen42 in #77
- Reclaim pages after segment compaction by @tjgreen42 in #78
- Add storage and query optimization roadmap by @tjgreen42 in #79
- Implement V2 segment format with block storage for BMW optimization by @tjgreen42 in #81
- Style benchmark graph points by branch type by @tjgreen42 in #84
- Fix V2 segment query performance regression by @tjgreen42 in #87
- Replace fixed-size registry with dshash for unlimited indexes by @tjgreen42 in #85
- fix: buildempty() should write init fork by @SteveLauC in #89
- Update v1.0.0 target date to Feb 2026 by @tjgreen42 in #97
- chore: fix make test and override pgxs installcheck by @SteveLauC in #91
- Refactor codebase to better reflect architectural structure by @tjgreen42 in #99
- Release v0.2.0 by @tjgreen42 in #100
New Contributors
- @SteveLauC made their first contribution in #89
Full Changelog: v0.1.0...v0.2.0