git/list[1] front-page[2] threads[3] people[4] search[5] about
 

How to reduce pickaxe times for a particular repo?

From
PRPavel Rappo <pavel.rappo@gmail.com>
Date
Jun 28, 2022, 10:50 UTC
Message-ID
<CAChcVumN66OxOjag9gPqgLq7gQrgdaEkZAJabusE-gGC7LLVyw@mail.gmail.com>
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

Next: Ævar Arnfjörð Bjarmason
Message 1 of 6 in “How to reduce pickaxe times for a particular repo?”
  1. Pavel RappoJun 28, 2022
  2. Ævar Arnfjörð BjarmasonJun 28, 2022
  3. Pavel RappoJun 28, 2022
  4. Ævar Arnfjörð BjarmasonJun 29, 2022
  5. Derrick StoleeJun 28, 2022
  6. Jeff KingJul 1, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.