From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Geoffrey Irving <irving@naml.us>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] Adding a cache of commit to patch-id pairs to speed up git-cherry
Date: Mon, 2 Jun 2008 02:42:18 -0400 [thread overview]
Message-ID: <20080602064218.GA15144@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0806020649110.13507@racer.site.net>
On Mon, Jun 02, 2008 at 07:13:14AM +0100, Johannes Schindelin wrote:
> I do not think that this "read-the-entire-table-into-memory" paradigm is a
> wise choice. mmap()ing, I would have understood, but reading a potentially
> pretty large table into memory?
When I was just a git-youth, I wrote a fast mmap-based cache for storing
SHA1 pairs. It might give some direction. You should be able to find it
here:
http://mid.gmane.org/20060629035849.GA30749@coredump.intra.peff.net
It mmaps and binary searches a sorted list. New entries are added to an
in-memory list, and then at the end of a run, the two sorted lists are
merged to create the new on-disk version.
-Peff
next prev parent reply other threads:[~2008-06-02 6:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 3:54 [PATCH] Adding a cache of commit to patch-id pairs to speed up git-cherry Geoffrey Irving
2008-06-02 6:13 ` Johannes Schindelin
2008-06-02 6:42 ` Jeff King [this message]
2008-06-02 14:35 ` Geoffrey Irving
2008-06-02 15:37 ` Johannes Schindelin
2008-06-02 15:49 ` Geoffrey Irving
2008-06-02 15:56 ` Shawn O. Pearce
2008-06-02 16:18 ` Johannes Schindelin
2008-06-02 16:26 ` Geoffrey Irving
2008-06-02 18:15 ` Johannes Schindelin
2008-06-07 23:50 ` Geoffrey Irving
2008-06-08 16:10 ` Johannes Schindelin
2008-06-02 14:50 ` Geoffrey Irving
2008-06-02 15:52 ` Johannes Schindelin
2008-06-02 17:23 ` Geoffrey Irving
2008-06-02 18:22 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080602064218.GA15144@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=irving@naml.us \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).