From: "Marco Costalba" <mcostalba@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: QGit: Shrink used memory with custom git log format
Date: Sat, 24 Nov 2007 09:14:42 +0100 [thread overview]
Message-ID: <e5bfff550711240014n78f24b46qf012957d92b1a8e1@mail.gmail.com> (raw)
Hi all,
I have pushed a patch series to
git://git.kernel.org/pub/scm/qgit/qgit4.git
that changes the format of git log used to read data from a git repository.
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.
Marco
next reply other threads:[~2007-11-24 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 8:14 Marco Costalba [this message]
2007-11-27 1:52 ` QGit: Shrink used memory with custom git log format Shawn O. Pearce
2007-11-27 10:48 ` Johannes Schindelin
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=e5bfff550711240014n78f24b46qf012957d92b1a8e1@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.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).