Re: Poor performance of git describe in big repos
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- May 30, 2013, 13:45 UTC
- Message-ID
- <CACsJy8AuhbwkjGjeQRYe1XZFsAntNdpKYxBM9aeMwF3HpB16Ow@mail.gmail.com>
- In-Reply-To
- <CAJ-05NPacjAEC99Ntd9eMnTD9_PMMYFob-_tAx5CeSB79TkRSg@mail.gmail.com>
On Thu, May 30, 2013 at 8:34 PM, Alex Bennée <kernel-hacker@bennee.com> wrote:
Show 18 quoted lines
> From the following run: > > > 14:31 ajb@sloy/x86_64 [work.git] >time /usr/bin/git --no-pager > describe --long --tags > ajb-build-test-5224-11-g9660048 > > real 0m14.720s > user 0m12.985s > sys 0m1.700s > 14:31 ajb@sloy/x86_64 [work.git] >wc -l /tmp/log-pack.txt > 1610 /tmp/log-pack.txt > > The pack has been "tuned" with a gc --aggressive. Assuming the numbers > are offsets into the pack it looks fairly random access until the last > 100 or so. > > [snipped]
Thanks. Can you share "verify-pack -v" output of pack-a9ba133a6f25ffa74c3c407e09ab030f8745b201.pack? I think you need to put it somewhere on Internet temporarily as it's likely to exceed git@vger limits. -- Duy