From: Jakub Narebski <jnareb@gmail.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Joshua Juran <jjuran@gmail.com>,
Finn Arne Gangstad <finnag@pvv.org>,
git@vger.kernel.org
Subject: Re: inotify daemon speedup for git [POC/HACK]
Date: Wed, 28 Jul 2010 06:09:55 -0700 (PDT) [thread overview]
Message-ID: <m3pqy7kb2z.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimkLrTwavErFkyaUTSVU-2s3me5f+cyqNFp7n+D@mail.gmail.com>
Avery Pennarun <apenwarr@gmail.com> writes:
> For speed, the bup index can just mark entries as deleted using a flag
> rather than actually rewriting the whole indexfile. Unfortunately, I
> failed to make it sufficiently flexible to *add* new entries without
> needing to rewrite the whole thing. In bup, that's a big deal
> (especially since python is kind of slow and there are typically >1
> million files in the index). In git, it's maybe not so bad; after
> all, the current implementation rewrites the index *every* time and
> nobody notices.
Sidenote: couldn't you do what e.g. Mercurial did, i.e. rewrite
critical for performance parts in C?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-07-28 13:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 12:20 inotify daemon speedup for git [POC/HACK] Finn Arne Gangstad
2010-07-27 23:29 ` Avery Pennarun
2010-07-27 23:39 ` Joshua Juran
2010-07-27 23:51 ` Avery Pennarun
2010-07-28 0:00 ` Shawn O. Pearce
2010-07-28 0:18 ` Avery Pennarun
2010-07-28 1:14 ` Joshua Juran
2010-07-28 1:31 ` Avery Pennarun
2010-07-28 6:03 ` Sverre Rabbelier
2010-07-28 6:06 ` Jonathan Nieder
2010-07-28 7:44 ` Ævar Arnfjörð Bjarmason
2010-07-28 11:08 ` Theodore Tso
2010-07-28 8:20 ` Nguyen Thai Ngoc Duy
2010-08-13 17:53 ` Enrico Weigelt
2010-07-28 13:09 ` Jakub Narebski [this message]
2010-07-28 13:06 ` Jakub Narebski
2010-08-13 17:58 ` Enrico Weigelt
2010-07-27 23:58 ` Sverre Rabbelier
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=m3pqy7kb2z.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=apenwarr@gmail.com \
--cc=finnag@pvv.org \
--cc=git@vger.kernel.org \
--cc=jjuran@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.