You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
perf: replace causal scan in find_last_delete_op with peer-by-peer range scan (#978)
iter_changes_causally_rev walks every change in the oplog in DAG order,
which is O(total changes). Any delete op covering `id` must have observed
it, so start_vv (the vv at `id`) is a valid lower bound per peer. Switching
to iter_changes_peer_by_peer with that bound skips all changes that predate
`id` without needing causal ordering. The match with the highest lamport
timestamp is the latest delete.
0 commit comments