phases: avoid N² behavior in `advanceboundary`
We allowed duplicated entries in the deque, which each entry could potentially insert all its ancestors. So advancing boundary for the full repository would mean each revision would walk all its ancestors, resulting in O(N²) iteration. For repository of any decent size, N² is quickly insane. We introduce a simple set to avoid this and get back to reasonable performance.
parent
6b2aeeec3ed0
No related branches found
No related tags found
Loading
-
mentioned in commit 7c83f0e82f70
-
mentioned in commit 4976aacae424
Please register or sign in to comment