From: Michael J Gruber <git@drmicha.warpmail.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Nick Edelen <sirnot@gmail.com>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Sam Vilain <sam@vilain.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
Andreas Ericsson <exon@op5.se>,
Christian Couder <christian@couder.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 0/5] Suggested for PU: revision caching system to significantly speed up packing/walking
Date: Thu, 06 Aug 2009 16:58:48 +0200 [thread overview]
Message-ID: <4A7AEFA8.5010001@drmicha.warpmail.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0908061645470.8306@pacific.mpi-cbg.de>
Johannes Schindelin venit, vidit, dixit 06.08.2009 16:48:
> Hi,
>
> On Thu, 6 Aug 2009, Nick Edelen wrote:
>
>> SUGGESTED FOR 'PU':
>>
>> 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.
>>
>> This is a series to implement such a revision caching mechanism, aptly named
>> rev-cache. The series will provide:
>> - a core API to manipulate and traverse caches
>> - an integration into the internal revision walker
>> - a porcelain front-end providing access to users and (shell) applications
>> - a series of tests to verify/demonstrate correctness
>> - documentation of the API, porcelain and core concepts
>>
>> In cold starts rev-cache has sped up packing and walking by a factor of 4, and
>> over twice that on warm starts. Some times on slax for the linux repository:
>>
>> rev-list --all --objects >/dev/null
>> default
>> cold 1:13
>> warm 0:43
>> rev-cache'd
>> cold 0:19
>> warm 0:02
>>
>> pack-objects --revs --all --stdout >/dev/null
>> default
>> cold 2:44
>> warm 1:21
>> rev-cache'd
>> cold 0:44
>> warm 0:10
>
> Nice!
>
>> The mechanism is minimally intrusive: most of the changes take place in
>> seperate files, and only a handful of git's existing functions are
>> modified.
>
> Sorry, I forgot the details, could you quickly remind me why these caches
> are not in the pack index files?
>
>> Documentation/rev-cache.txt | 51 +
>> Documentation/technical/rev-cache.txt | 336 ++++++
>> Makefile | 2 +
>> blob.c | 1 +
>> blob.h | 1 +
>> builtin-rev-cache.c | 284 +++++
>> builtin.h | 1 +
>> commit.c | 3 +
>> commit.h | 2 +
>> git.c | 1 +
>> list-objects.c | 49 +-
>> rev-cache.c | 1832 +++++++++++++++++++++++++++++++++
>> revision.c | 89 ++-
>> revision.h | 46 +-
>> t/t6015-rev-cache-list.sh | 228 ++++
>> t/t6015-sha1-dump-diff.py | 36 +
>
> Hmpf.
>
> We got rid of the last Python script in Git a long time ago, but now two
> different patch series try to sneak that dependency (at least for testing)
> back in.
>
> That's all the worse because we cannot use Python in msysGit, and Windows
> should be a platform benefitting dramatically from your work.
In fact, the test the script performs could be easily rephrased with
"sort", "uniq" and "comm".
OTOH: If the walker is supposed to return the exact same orderd list of
commits you can just use test_cmp.
Michael
next prev parent reply other threads:[~2009-08-06 14:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 9:55 [PATCH 0/5] Suggested for PU: revision caching system to significantly speed up packing/walking Nick Edelen
2009-08-06 14:48 ` Johannes Schindelin
2009-08-06 14:58 ` Michael J Gruber [this message]
2009-08-06 17:39 ` Nick Edelen
2009-08-06 19:06 ` Johannes Schindelin
2009-08-06 20:01 ` Nick Edelen
2009-08-06 20:30 ` Nick Edelen
2009-08-06 20:32 ` Shawn O. Pearce
2009-08-06 23:35 ` A Large Angry SCM
2009-08-06 23:37 ` Shawn O. Pearce
2009-08-06 23:43 ` A Large Angry SCM
2009-08-07 0:15 ` Nick Edelen
2009-08-07 6:05 ` Johannes Schindelin
2009-08-07 4:42 ` Nicolas Pitre
2009-08-07 2:47 ` Sam Vilain
2009-08-07 4:35 ` Nicolas Pitre
2009-08-07 6:08 ` Johannes Schindelin
2009-08-07 14:18 ` Nicolas Pitre
2009-08-08 15:18 ` Johannes Schindelin
2009-08-08 16:07 ` Junio C Hamano
2009-08-08 23:54 ` Sam Vilain
2009-08-09 2:37 ` Nicolas Pitre
2009-08-09 13:42 ` Nick Edelen
2009-08-07 6:12 ` Johannes Schindelin
2009-08-07 15:00 ` Nicolas Pitre
2009-08-07 22:02 ` Nick Edelen
2009-08-07 22:48 ` Junio C Hamano
2009-08-07 22:53 ` Nick Edelen
2009-08-08 3:11 ` Junio C Hamano
2009-08-08 7:27 ` Nick Edelen
2009-08-08 7:30 ` Jeff King
2009-08-08 7:40 ` Nick Edelen
2009-08-08 2:50 ` Jeff King
2009-08-08 18:57 ` Junio C Hamano
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=4A7AEFA8.5010001@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian@couder.net \
--cc=exon@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sam@vilain.net \
--cc=sirnot@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.