Re: Thoughts on gitk's memory footprint over linux-2.6.git

From: Elijah Newren <newren@gmail.com>
Date: Sep 26, 2011, 22:02 UTC
Message-ID: <CABPp-BHo5qKQVFRzFpoyt6dZZ3=UqVAtSjVy0uRDWnA+ASsBPw@mail.gmail.com>
In-Reply-To: <CACPiFC+T1EZ1CSakQxsYZhsnHc-ZsN1-=tpoi-NaQSdpU5Yxkg@mail.gmail.com>

On Mon, Sep 26, 2011 at 1:38 PM, Martin Langhoff <martin.langhoff@gmail.com> wrote:

Show 11 quoted lines

> In an odd turn of affairs, I am managing a bit of kernel development,
> and even writing the odd patch myself. As usual, gitk is excellent to
> visualize what's new in the tree when developers in the team commit
> and push new stuff.
>
> However, I find it extremely annoying over the kernel tree, due to its
> memory footprint. It is not the only thing I am running, (Chrome
> Browser, Gnome3, Firefox, many gnome Terminal windows, emacs), and
> given that I am looking at "just a couple of commits" I don't feel
> opening a few gitk instances should be problematic... except that it
> is.

If you only want to look at a couple commits, you could tell gitk that:
  gitk -N
where N is some small integer -- or even 10000, as you suggest.  Or
use other rev-list arguments, such as
  gitk v2.6.38..master

gitk and 'git log' accept basically the same arguments, so look at the help for git log if you want to find other example ways to slice and dice what pieces of history to view.

Hope that helps, Elijah