From: Eli Zaretskii <eliz@gnu.org>
To: Werner LEMBERG <wl@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: `bzr viz' slooow
Date: Tue, 26 Jan 2010 19:48:47 +0200 [thread overview]
Message-ID: <83eilc69kw.fsf@gnu.org> (raw)
In-Reply-To: <20100126.180554.173876640.wl@gnu.org>
> Date: Tue, 26 Jan 2010 18:05:54 +0100 (CET)
> From: Werner LEMBERG <wl@gnu.org>
>
>
> The most valuable tool of git is `gitk' to visualize changes together
> with the corresponding tree. The pendant is `bzr viz', using the
> `gtk' plugin for bazaar. However, it is very slow. Calling this
> command for the emacs trunk takes five minutes to start on my laptop
> with a a dual-core 1Ghz CPU having 1GByte of memory.
What kind of branch is your trunk? Is it according to the workflow in
the wiki page (i.e., a bound branch with local repository) or
something else?
Regardless, look in your .bzr.log file and tell us what part takes
most of the time in your frequent operations. Each line in the log
has a time stamp, so it's easy to see the sinks.
next prev parent reply other threads:[~2010-01-26 17:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 17:05 `bzr viz' slooow Werner LEMBERG
2010-01-26 17:48 ` Eli Zaretskii [this message]
2010-01-26 22:07 ` Werner LEMBERG
2010-01-27 4:11 ` Eli Zaretskii
2010-01-27 6:14 ` Werner LEMBERG
2010-01-27 11:29 ` Eli Zaretskii
2010-01-27 12:01 ` Werner LEMBERG
2010-01-27 13:03 ` Eli Zaretskii
2010-01-26 18:37 ` Óscar Fuentes
2010-01-26 22:16 ` Werner LEMBERG
2010-01-26 23:13 ` Óscar Fuentes
2010-01-27 6:15 ` Werner LEMBERG
2010-01-26 22:59 ` Dan Nicolaescu
2010-01-27 5:22 ` Ken Hori
2010-01-27 6:02 ` Werner LEMBERG
2010-01-27 11:10 ` Óscar Fuentes
2010-01-27 11:30 ` Werner LEMBERG
2010-01-27 11:51 ` Werner LEMBERG
2010-01-27 12:05 ` Eli Zaretskii
2010-01-27 12:27 ` Óscar Fuentes
2010-01-27 13:02 ` Eli Zaretskii
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=83eilc69kw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wl@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.