git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: ZheNing Hu <adlternative@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [hacky PATCH 0/2] speeding up trivial for-each-ref invocations
Date: Tue, 7 Sep 2021 13:28:31 -0400	[thread overview]
Message-ID: <YTehP58NfcnDSWEc@coredump.intra.peff.net> (raw)
In-Reply-To: <CAOLTT8SYx4f8x-0zjXLJVOpW4-Mj34mjsfwr6tWo0PbZAV9B0w@mail.gmail.com>

On Mon, Sep 06, 2021 at 09:30:45PM +0800, ZheNing Hu wrote:

> Jeff King <peff@peff.net> 于2021年9月5日周日 下午8:49写道:
> >
> > On Sun, Sep 05, 2021 at 04:19:53PM +0800, ZheNing Hu wrote:
> >
> > > > In this version there are 2 patches, tested against 'git for-each-ref
> > > > --format="%(objectname) %(refname)"' on a fully packed repo with 500k
> > > > refs:
> > > >
> > >
> > > Regarding this 500k refs, is there any way I can reproduce it?
> >
> > Try this in a clone of linux.git (or any other repo):
> >
> >   git rev-list HEAD |
> >   head -500000 |
> >   perl -lne 'print "create refs/foo/$. $_"' |
> >   git update-ref --stdin
> >
> >   git pack-refs --all --prune
> >
> 
> Sorry, It seems that the above command is difficult to complete on my
> machine (it took more than ten minutes). It may be stuck on git update-ref.
> So I tried to reproduce it in a repo which containing 76K refs:

Mine didn't take nearly that wrong, but it does depend on filesystem and
disk performance. It's going to create 500k lock files in refs/foo. :)

You can cheat a bit like this:

  {
    # grab existing packed refs; don't worry about peel lines or the
    # header comment, we're producing a lowest-common denominator
    # version of the file
    grep '^[0-9a-f]' packed-refs

    # now make our new fake refs
    git rev-list HEAD |
    head -500000 |
    perl -lne 'print "$_ refs/foo/$."'
  } >packed-refs.tmp
  mv packed-refs.tmp packed-refs

  # and now ask Git to repack to get everything sorted, etc
  git pack-refs --all --prune

It sounds like you were able to come up with a smaller version to play
with anyway, but I enjoy coming up with such hacks. :)

-Peff

  reply	other threads:[~2021-09-07 17:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 12:40 Jeff King
2021-09-04 12:41 ` [PATCH 1/2] ref-filter: hacky "streaming" mode Jeff King
2021-09-05  8:20   ` ZheNing Hu
2021-09-05 13:04     ` Jeff King
2021-09-07  5:28       ` ZheNing Hu
2021-09-07 18:01         ` Jeff King
2021-09-09 14:45           ` ZheNing Hu
2021-09-10 14:26             ` Jeff King
2021-09-15 12:27               ` ZheNing Hu
2021-09-15 14:23                 ` ZheNing Hu
2021-09-16 21:45                   ` Jeff King
2021-09-20  7:42                     ` ZheNing Hu
2021-09-16 21:31                 ` Jeff King
2021-09-05 13:15     ` Jeff King
2021-09-07  5:42       ` ZheNing Hu
2021-09-04 12:42 ` [PATCH 2/2] ref-filter: implement "quick" formats Jeff King
2021-09-05  8:20   ` ZheNing Hu
2021-09-05 13:07     ` Jeff King
2021-09-06 13:34       ` ZheNing Hu
2021-09-07 20:06       ` Junio C Hamano
2021-09-05  8:19 ` [hacky PATCH 0/2] speeding up trivial for-each-ref invocations ZheNing Hu
2021-09-05 12:49   ` Jeff King
2021-09-06 13:30     ` ZheNing Hu
2021-09-07 17:28       ` Jeff King [this message]
2021-09-09 13:20         ` ZheNing Hu
2021-09-06  6:54 ` Patrick Steinhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YTehP58NfcnDSWEc@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=adlternative@gmail.com \
    --cc=git@vger.kernel.org \
    --subject='Re: [hacky PATCH 0/2] speeding up trivial for-each-ref invocations' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).