Feature/Fix: Profile and optimize shadow lineage accounting#44
Open
iam-brain wants to merge 2 commits into
Open
Feature/Fix: Profile and optimize shadow lineage accounting#44iam-brain wants to merge 2 commits into
iam-brain wants to merge 2 commits into
Conversation
This was referenced Jul 13, 2026
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
This is another isolated component of the planned scanner rearchitecture tracked in #10. It keeps lineage accounting in shadow mode and does not remove the legacy fallback.
Real-data validation
On the retained 570-document / 819,779-observation corpus, daily UTC totals stayed identical while lineage runtime fell from about 225s in the instrumented baseline to about 164s. Compared with the earlier roughly 360s replay, the current path is about 54% faster. Family reconciliation dropped from 72.4s to 15.2s; discovery and document loading remain the next performance constraints.
Tests
swift test --filter CodexLineageEngineTests --filter CodexLineageTwoPassDiscoveryTests --filter CodexLineageLedgerTestsmake checkmake test(649 selections, 55/55 groups, no failures, retries, or timeouts)Closes #42.