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

Re: [RFC] super indexes to span multiple packfiles

From
AKAvi Kivity <avi@qumranet.com>
Date
May 29, 2007, 16:20 UTC
Message-ID
<465C52D3.3010605@qumranet.com>
In-Reply-To
<9e4733910705290905m66dd3081ubda9b92a707fc903@mail.gmail.com>
Jon Smirl wrote:
Show 6 quoted lines
>
> My work with databases leads me to believe that figuring out how to
> pack everything into a smaller space always beats efforts put into
> incrementally improving the indexing scheme. Packing into a smaller
> space reduces the total IO needs and that's always a winner.
>

Another way to achieve that is to place objects that are accessed together nearby, and issue a larger read so as to bring them into cache. I imagine that placing commit objects and associated tree and blobs in history order should help here (but maybe git already does that, I'm not familiar with the internals).

-- 
error compiling committee.c: too many arguments to function
Previous: Nicolas PitreNext: Nicolas Pitre
Message 4 of 7 in “[RFC] super indexes to span multiple packfiles”
  1. Shawn O. PearceMay 29, 2007
  2. Jon SmirlMay 29, 2007
  3. Nicolas PitreMay 29, 2007
  4. Avi KivityMay 29, 2007
  5. Nicolas PitreMay 29, 2007
  6. Avi KivityMay 30, 2007
  7. Geert BoschMay 29, 2007

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.