On Mon, Jul 7, 2025, 3:43 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Phil Hord <phil.hord@xxxxxxxxx> writes: > > > From: Phil Hord <phil.hord@xxxxxxxxx> > > > > `git fetch --prune` runs in O(N^2) time normally. This happens because the code > > iterates over each ref to be pruned to display its status. In a repo with > > 174,000 refs, where I was pruning 15,000 refs, the current code made 2.6 billion > > calls to strcmp and consumed 470 seconds of CPU. After this change, the same > > operation completes in under 1 second. > > ... > > V3 forgot to include the first commit in the series (I forgot it grew). > > So here's V4. > > > > Phil Hord (3): > > fetch-prune: optimize dangling-ref reporting > > refs: remove old refs_warn_dangling_symref > > clean up interface for refs_warn_dangling_symrefs > > It seems that the thread has gone quiet. What's the status of this > topic? > > Thanks. LGTM
