Repository navigation
perf(capture): avoid session scans for durable replays - #1773
zack-dev-cm wants to merge 2 commits into
Conversation
Signed-off-by: zack-dev-cm <112114097+zack-dev-cm@users.noreply.github.com>
|
@zack-dev-cm is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Signed-off-by: zack-dev-cm <112114097+zack-dev-cm@users.noreply.github.com>
|
Merged as part of #1811, which kept your commits and added review fixes on top (details in its description). Thanks for the contribution. |
Durable observation replays currently load the whole session before finding an already-stored record. Read its key first, validate the stored ID, and use the existing list lookup when the point read fails, misses, or finds a mismatched record.
Keep the session lock, live-prompt bookkeeping and index repair. New observations still load the existing rows for source budgeting and cap eviction. This implements the dedup-lookup part of #1734; the compression path and running byte totals remain separate.
Validation:
Refs #1734
Summary by CodeRabbit