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

Re: [PATCH 2/2] repack: repack promisor objects if -a or -A is set

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 8, 2018, 16:17 UTC
Message-ID
<xmqqin4kj0j0.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20180808155045.GB1607@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> I think that the for_each_packed_object() interface should visit items
> in pack order.

Yeah, that may make more sense. Any order is more logical than the object name order (which by definition is random, so useful only when you want them in a random order), and pack order will give us locality of accesses.

>    For traversals using bitmaps, we have a "name hash cache" in the
>    .bitmap file, which stores the 32-bit hash of the name. That lets us
>    put similar names next to each other without actually knowing the
>    names.

I forgot about that one; it is a neat trick. As .primisor packs are intentionally kept apart from the remainder of the repository, and because .bitmap wants to have a single pack, we cannot just read the .bitmap file for this particular application, though.

Previous: Jeff KingNext: Junio C Hamano
Message 9 of 18 in “Repacking of promisor packfiles”
  1. 0/2 Repacking of promisor packfilesJonathan Tan, Aug 7, 2018
  2. 1/2 repack: refactor setup of pack-objects cmdJonathan Tan, Aug 7, 2018
  3. 2/2 repack: repack promisor objects if -a or -A is setJonathan Tan, Aug 7, 2018
  4. Junio C HamanoAug 7, 2018
  5. Jonathan TanAug 7, 2018
  6. Junio C HamanoAug 8, 2018
  7. Jonathan TanAug 8, 2018
  8. Jeff KingAug 8, 2018
  9. Junio C HamanoAug 8, 2018
  10. Junio C HamanoAug 7, 2018
  11. Jonathan TanAug 7, 2018
  12. Junio C HamanoAug 8, 2018
  13. 0/2 Repacking of promisor packfilesJonathan Tan, Aug 8, 2018
  14. 1/2 repack: refactor setup of pack-objects cmdJonathan Tan, Aug 8, 2018
  15. 2/2 repack: repack promisor objects if -a or -A is setJonathan Tan, Aug 8, 2018
  16. Junio C HamanoAug 9, 2018
  17. Jonathan TanAug 9, 2018
  18. Duy NguyenAug 18, 2018

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.