From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Marco Costalba <mcostalba@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: QGit: Shrink used memory with custom git log format
Date: Tue, 27 Nov 2007 10:48:00 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711271045430.27959@racer.site> (raw)
In-Reply-To: <20071127015248.GK14735@spearce.org>
Hi,
On Mon, 26 Nov 2007, Shawn O. Pearce wrote:
> Marco Costalba <mcostalba@gmail.com> wrote:
> > Now instead of --pretty=raw a custom made --pretty=format is given,
> > this shrinks loaded data of 30% (17MB less on Linux tree) and gives a
> > good speed up when you are low on memory (especially on big repos)
> >
> > Next step _would_ be to load log message body on demand (another 50%
> > reduction) but this has two drawbacks:
> >
> > (1) Text search/filter on log message would be broken
> >
> > (2) Slower to browse through revisions because for each revision an
> > additional git-rev-list /git-log command should be executed to read
> > the body
> >
> > The second point is worsted by the fact that it is not possible to
> > keep a command running and "open" like as example git-diff-tree
> > --stdin and feed with additional revision's sha when needed. Avoiding
> > the burden to startup a new process each time to read a new log
> > message given an sha would let the answer much more quick especially
> > on lesser OS's
> >
> > Indeed there is a git-rev-list --stdin option but with different
> > behaviour from git-diff-tree --stdin and not suitable for this.
>
> There was a proposed patch for git-cat-file that would let you run
> it in a --stdin mode; the git-svn folks wanted this to speed up
> fetching raw objects from the repository. That may help as you
> could get commit bodies (in raw format - not reencoded format!)
> quite efficiently.
>
> Otherwise I think what you really want here is a libgit that you can
> link into your process and that can efficiently inflate an object
> on demand for you. Like the work Luiz was working on this past
> summer for GSOC. Lots of downsides to that current tree though...
> like die() kills the GUI...
But then, die() calls die_routine, which you can override. And C++ has
this funny exception mechanism which just begs to be used here. The only
thing you need to add is a way to flush all singletons like the object
array.
Ciao,
Dscho
next prev parent reply other threads:[~2007-11-27 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 8:14 QGit: Shrink used memory with custom git log format Marco Costalba
2007-11-27 1:52 ` Shawn O. Pearce
2007-11-27 10:48 ` Johannes Schindelin [this message]
2007-11-27 12:36 ` Marco Costalba
2007-11-27 19:19 ` Jan Hudec
2007-11-28 12:01 ` Johannes Schindelin
2007-11-28 15:53 ` jhud7196
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=Pine.LNX.4.64.0711271045430.27959@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mcostalba@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 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 NNTP newsgroup(s).