From: "David Tweed" <david.tweed@gmail.com>
To: "Paul Mackerras" <paulus@samba.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: gitk performance questions/issues
Date: Tue, 14 Aug 2007 12:25:59 +0100 [thread overview]
Message-ID: <e1dab3980708140425r72733f1bn4bc0d2e6cc68fb4c@mail.gmail.com> (raw)
In-Reply-To: <18113.12777.164103.302185@cargo.ozlabs.ibm.com>
On 8/14/07, Paul Mackerras <paulus@samba.org> wrote:
> David Tweed writes:
> Could you try this: go to the Edit->Preferences window and turn off
> "Display nearby tags". Then with your ~2000 refs in place, see how
> long gitk takes to start up and to display a diff.
Right, I've restored the file of 1915 packed tags (but not the 35 loose
tags). Using DNT for "display nearby tags"
DNT on: consistently 11s to window appear, 20s to normal cursor
DNT off: consistently 11s to window appear but normal cursor immediately
Regarding getting the diffs, I think that was "user misunderstanding" and
I'm doubting if I definitely did click on the blue circles yesterday. Clicking
on the any part yellow tag marker displays the SHA of the tag object
(which I'd confused with the start of an unfinished commit diff);
for some reason I'd thought it would give the diff-with-parent. Clicking on
either the blue circle or "commit headline text" does bring up the diff
instantly even with the packed refs file. Sorry for the confusion.
> Also, if it's possible to give me a copy of your repo, that would
> help.
I'll privately mail Paul about getting it; if anyone else wants a copy
of the repository
in order look at startup performance issues mail me. (The most embarassing
thing in there is just some astonishingly crap code, but I'd prefer not to
blanket publish it.)
--
cheers, dave tweed__________________________
david.tweed@gmail.com
Rm 124, School of Systems Engineering, University of Reading.
"we had no idea that when we added templates we were adding a Turing-
complete compile-time language." -- C++ standardisation committee
prev parent reply other threads:[~2007-08-14 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 9:48 gitk performance questions/issues David Tweed
2007-08-13 16:59 ` Linus Torvalds
2007-08-13 17:18 ` David Tweed
2007-08-14 4:39 ` Paul Mackerras
2007-08-14 11:25 ` David Tweed [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=e1dab3980708140425r72733f1bn4bc0d2e6cc68fb4c@mail.gmail.com \
--to=david.tweed@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.org \
--cc=torvalds@linux-foundation.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).