Repository navigation
perf(mail): re-indexing after a large rules change - #73
Merged
Merged
Conversation
…to repeat Why the scheduled memo sync held the import lock for hours after 44,011 emails were cut to envelopes (PERF-42): the index drain deleted vectors by hash alone and scanned the whole vector table per hash. Totals before and after cli-core#1259, and run.sh to repeat it on a store copy. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Why the scheduled memo sync held the import lock for hours after 44,011 emails were cut to envelopes (PERF-42), measured on a store copy: the index drain deleted vectors by hash alone, scanning all 28,342 vectors per hash. Whole queue (13,157 threads): 896 s before, 3.4 s after cli-core#1259. Totals only;
run.shrepeats it.🤖 Generated with Claude Code