Re: [PATCH 0/2] status: stop holding index.lock while collecting
Mihai Cosma <mcosma@gmail.com> writes:
Show 7 quoted lines
> This overlaps with Jun Wu's "Wait for the index lock instead of
> failing" series, and the two fit together: his makes writers wait for
> the lock, this makes status hold it rarely and briefly. They only
> conflict on the one lock call in cmd_status(), which his series renames
> to repo_try_hold_locked_index(). I'm happy to rebase onto it. On top of
> his v2, the slowest "git add" in the clean case below went from 1020 ms
> (one failure at his 1s timeout) to 160 ms.
Perhaps you two can work together and send a single consolidated series?
Thanks.