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

Re: [RFC/PATCH 1/4] rev-cache: basic implementation + full docs + tests

From
Alex Riesen <raa.lkml@gmail.com>
Date
Jul 3, 2009, 21:43 UTC
Message-ID
<81b0412b0907031443r1c49e8c4r598b3cf16eb641a8@mail.gmail.com>
In-Reply-To
<op.uwhy8r14tdk399@sirnot>
On Fri, Jul 3, 2009 at 17:13, Nick Edelen<sirnot@gmail.com> wrote:
> Traversing objects is currently very costly, as every commit and tree must be loaded and parsed.  Much time and energy could be saved by caching metadata and topological info in an efficient, easily accessible manner.  Furthermore, this could improve git's interfacing potential, by providing a condensed summary of a repository's commit tree.

Do you have any benchmarks? How much improvement does it mean for _common_ operations?

Previous: Nick Edelen
Message 2 of 2 in “rev-cache: basic implementation + full docs + tests”
  1. 1/4 rev-cache: basic implementation + full docs + testsNick Edelen, Jul 3, 2009
  2. Alex RiesenJul 3, 2009

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.