perf: remove global scans and quadratic temporal processing - #10
Merged
Merged
Conversation
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.
Persistent ingestion repeatedly scanned unrelated global-ID and boundary state on ordinary duplicate merges, while temporal history processing performed several Cartesian scans. This change removes that repeated work while preserving entity resolution, temporal component guards, canonical IDs and synchronous durable acknowledgements.
On five local persistent shards, three paired one-million-record runs per revision improved median throughput by 45.8% with 10% generated overlap and 46.9% with 0% generated overlap. A single two-million-record comparison improved throughput by 84.7%. All 16 million comparative records were acknowledged with zero failed batches. Focused long-history golden queries improved up to 261×; that ratio is specific to the diagnostic workload. No measured workload regressed, but these results do not establish universal capacity or linear engine scaling.
See the analysis and raw results for workload details, methods and limitations.
Local validation passed: 371 tests, zero failures (7 intentionally ignored diagnostics/examples); focused release timing diagnostics; Rust 1.88 all-target/all-feature compatibility; Rust 1.98 strict Clippy; formatting; strict Rustdoc; release-package verification; and relative documentation links. All GitHub CI checks passed: Linux build/tests, strict documentation/lints, package and deployment-manifest validation, MSRV, and the production-container build.