From: Jeff King <peff@peff.net>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: David Barr <davidbarr@google.com>,
elton sky <eltonsky9404@gmail.com>,
Shawn Pearce <spearce@spearce.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: GSoC - Designing a faster index format
Date: Thu, 29 Mar 2012 05:45:54 -0400 [thread overview]
Message-ID: <20120329094554.GA11603@sigill.intra.peff.net> (raw)
In-Reply-To: <CACsJy8BfCpH3jtfaOyyAgjH3P5fv4FYjboqjoFYF2GiG44TmoA@mail.gmail.com>
On Tue, Mar 27, 2012 at 01:33:33PM +0700, Nguyen Thai Ngoc Duy wrote:
> On Tue, Mar 27, 2012 at 10:34 AM, David Barr <davidbarr@google.com> wrote:
> > Another implementation in this general class is TinyCDB[1].
> > It is <1600 lines of plain C. Too few to be complete?
> > It is a derivative of DJB's CDB[2].
> >
> > [1] http://www.corpit.ru/mjt/tinycdb.html
>
> "CDB is a constant database, that is, it cannot be updated at a
> runtime, only rebuilt.". It does not sound promising to me. I have not
> read the description carefully though.
No, you are right. I did some work with cdb many years ago. It optimizes
for lookup by spending time building an optimal hash table at generation
time. There is no way to add or modify an entry short of rewriting the
complete contents of the database, which is exactly what we are trying
to get away from with the current index format.
-Peff
next prev parent reply other threads:[~2012-03-29 9:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 23:10 GSoC - Designing a faster index format elton sky
2012-03-21 1:18 ` Nguyen Thai Ngoc Duy
2012-03-21 11:25 ` Thomas Rast
2012-03-21 12:01 ` elton sky
2012-03-22 20:32 ` elton sky
2012-03-23 0:46 ` Jakub Narebski
2012-03-23 1:30 ` Nguyen Thai Ngoc Duy
2012-03-23 10:27 ` elton sky
2012-03-23 11:24 ` Nguyen Thai Ngoc Duy
[not found] ` <CAKTdtZmLOzAgG0uCDcVr+O41XPX-XnoVZjsZWPN-BLjq2oG-7A@mail.gmail.com>
2012-03-24 8:58 ` Nguyen Thai Ngoc Duy
[not found] ` <CAKTdtZkpjVaBSkcieojKj+V7WztT3UDzjGfXyghY=S8mq+X9zw@mail.gmail.com>
[not found] ` <CACsJy8D85thmK_5jLC7MxJtsitLr=zphKiw2miwPu7Exf7ty=Q@mail.gmail.com>
2012-03-26 12:36 ` elton sky
2012-03-26 12:41 ` elton sky
2012-03-26 14:28 ` Thomas Rast
2012-03-26 15:25 ` Nguyen Thai Ngoc Duy
2012-03-26 16:08 ` Shawn Pearce
2012-03-27 2:49 ` elton sky
2012-03-27 3:34 ` David Barr
2012-03-27 6:33 ` Nguyen Thai Ngoc Duy
2012-03-29 9:45 ` Jeff King [this message]
2012-03-27 6:31 ` Nguyen Thai Ngoc Duy
2012-03-26 16:19 ` Nguyen Thai Ngoc Duy
2012-03-27 3:20 ` elton sky
2012-03-27 6:43 ` Nguyen Thai Ngoc Duy
2012-04-02 11:50 ` elton sky
2012-04-02 12:31 ` Nguyen Thai Ngoc Duy
2012-04-02 14:27 ` Shawn Pearce
2012-04-02 15:12 ` Nguyen Thai Ngoc Duy
2012-04-04 8:26 ` elton sky
2012-04-04 12:20 ` Nguyen Thai Ngoc Duy
2012-04-04 16:22 ` elton sky
2012-04-06 3:13 ` elton sky
2012-04-06 3:15 ` elton sky
2012-04-07 8:29 ` elton sky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120329094554.GA11603@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=davidbarr@google.com \
--cc=eltonsky9404@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=spearce@spearce.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.