From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Roger C. Soares" <rogersoares@intelinet.com.br>
Cc: Robin Rosenberg <robin.rosenberg@dewire.com>, git@vger.kernel.org
Subject: Re: faster egit history page and a pure java "gitk"
Date: Wed, 26 Mar 2008 00:52:44 -0400 [thread overview]
Message-ID: <20080326045244.GH4759@spearce.org> (raw)
In-Reply-To: <47E9A8BE.4010606@intelinet.com.br>
"Roger C. Soares" <rogersoares@intelinet.com.br> wrote:
> Shawn O. Pearce escreveu:
> >Hmm. How long does C Git take for "git rev-list HEAD >/dev/null" ?
> >I have thus far only tuned the lower level machinary, and there
> >may still be tuning left there, but I _really_ have not tried to
> >tune the plotting portion yet.
> >
> >I did push something out a few minutes ago (b66eae Limit the number
> >of UI refreshes ...) that may help improve performance on larger
> >histories.
>
> "git rev-list HEAD >/dev/null" returns very fast, around 1 sec I'd say.
> My git clone has 0 loose objects and 1 pack.
OK, so its well packed and C Git behaves nicely. :)
> I updated from your repo some minutes ago and it's pretty decent now.
> The history appears very fast, even changing projects, and for the git
> clone the progress bar disapears in around 7 seconds. :)
So it must have been the massive flurry of UI updates that I used to
be doing during revision walking. I backed it off to at most 4 times
per second, which seems to help.
FWIW I just pushed another update out:
* re-activates the old preferences for hiding/showing the commit
message and file list;
* word wrap setting for the comment viewer area;
* saves the geometry (split pane positions) of the history page
in a hidden preference;
* copy and select all global actions (Edit->Copy aka Ctrl-C) now
works to copy:
- selected text in comment area;
- selected path names in the file list;
- commit SHA-1s of selected commits in DAG;
* the window cache is now managed by Eclipse workspace settings
when inside Eclipse;
* the window cache now defaults to 8k/10m/10m/no-mmap as that is
working very well for me on multiple systems;
* global workspace preferences (Team -> Git) now shows the history
preferences and the window cache settings
--
Shawn.
prev parent reply other threads:[~2008-03-26 4:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 9:27 faster egit history page and a pure java "gitk" Shawn O. Pearce
2008-03-24 13:33 ` Roger C. Soares
2008-03-24 14:10 ` Robin Rosenberg
2008-03-25 4:43 ` Shawn O. Pearce
2008-03-25 12:33 ` Roger C. Soares
2008-03-24 14:06 ` Robin Rosenberg
2008-03-25 5:10 ` Shawn O. Pearce
2008-03-24 14:31 ` faster egit history page and a pure java "gitk" so Robin Rosenberg
2008-03-25 4:48 ` Shawn O. Pearce
2008-03-25 5:07 ` faster egit history page and a pure java "gitk" Roger C. Soares
2008-03-25 5:36 ` Shawn O. Pearce
2008-03-25 8:09 ` Shawn O. Pearce
2008-03-25 13:46 ` Roger C. Soares
2008-03-25 19:48 ` Robin Rosenberg
2008-03-26 1:37 ` Roger C. Soares
2008-03-26 4:52 ` Shawn O. Pearce [this message]
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=20080326045244.GH4759@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.com \
--cc=rogersoares@intelinet.com.br \
/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).