Repository navigation
perf(post-1.0): B+Tree selective lookup for bound patterns #208
Description
Roadmap source
ROADMAP.md: Post-1.0 Performance Backlog.
Problem
filter_facts_for_query step 1 calls get_all_facts(), causing a full B+tree range scan even when a query binds a concrete entity or attribute that could use existing EAVT/AEVT indexes.
Proposed fix
Inspect query patterns before calling get_all_facts(). If a pattern binds a concrete entity or entity+attribute, use get_facts_by_entity / get_facts_by_attribute to fetch only the relevant subset.
Acceptance criteria
- Use selective index-backed fetches for eligible bound patterns.
- Keep existing snapshot/retraction/valid-time semantics intact.
- Add tests for entity-bound and attribute-bound queries.
- Add benchmarks showing sub-linear behavior for point entity/attribute queries.
Activity
feat: selective B+Tree lookup in filter_facts_for_query (#208) (#246)
docs: add Wave 1 performance design spec (#208, #202, #203, #204)
docs: add Wave 1 implementation plans for #208 and #202/#203/#204
docs: sync all docs for Wave 1 performance completion
docs: update BENCHMARKS.md Known Limitations — selective lookup and p…
docs: update benchmark baselines for v1.1.1 (#280)