git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Rappo <pavel.rappo@gmail.com>
To: Git mailing list <git@vger.kernel.org>
Subject: How to reduce pickaxe times for a particular repo?
Date: Tue, 28 Jun 2022 11:50:49 +0100	[thread overview]
Message-ID: <CAChcVumN66OxOjag9gPqgLq7gQrgdaEkZAJabusE-gGC7LLVyw@mail.gmail.com> (raw)

I have a repo of the following characteristics:

  * 1 branch
  * 100,000 commits
  * 1TB in size
  * The tip of the branch has 55,000 files
  * No new commits are expected: the repo is abandoned and kept for
archaeological purposes.

Typically, a `git log -S/-G` lookup takes around a minute to complete.
I would like to significantly reduce that time. How can I do that? I
can spend up to 10x more disk space, if required. The machine has 10
cores and 32GB of RAM.

Thanks,
-Pavel

             reply	other threads:[~2022-06-28 10:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 10:50 Pavel Rappo [this message]
2022-06-28 11:35 ` How to reduce pickaxe times for a particular repo? Ævar Arnfjörð Bjarmason
2022-06-28 12:35   ` Pavel Rappo
2022-06-29 12:31     ` Ævar Arnfjörð Bjarmason
2022-06-28 13:01 ` Derrick Stolee
2022-07-01 18:21   ` Jeff King

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=CAChcVumN66OxOjag9gPqgLq7gQrgdaEkZAJabusE-gGC7LLVyw@mail.gmail.com \
    --to=pavel.rappo@gmail.com \
    --cc=git@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).