unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Werner LEMBERG <wl@gnu.org>
To: eliz@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: `bzr viz' slooow
Date: Tue, 26 Jan 2010 23:07:24 +0100 (CET)	[thread overview]
Message-ID: <20100126.230724.243028555.wl@gnu.org> (raw)
In-Reply-To: <83eilc69kw.fsf@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?

I've no idea.  How can I find it out?  Below the `emacs' directory I
have a `.bzr' directory with about 275MByte and a `trunk' directory
with about 116MByte.  If I do a `bzr pull' I change into `trunk'.  The
same for `bzr viz'.

BTW, `bzr info' within `trunk' gives

  Repository tree (format: 2a)
  Location:
    shared repository: /home/wl/bzr/emacs
    repository branch: .

  Related branches:
    parent branch: sftp://wl@bzr.savannah.gnu.org/srv/bzr/emacs/trunk/

> Is it according to the workflow in the wiki page (i.e., a bound
> branch with local repository) or something else?

I checked it out about a month ago; at that time those infos weren't
available at all...

> 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.

Do you mean this?

  0.048  bzr arguments: [u'viz']
  0.066  looking for plugins in /home/wl/.bazaar/plugins
  0.066  looking for plugins in /usr/lib/python2.6/site-packages/bzrlib/plugins
  0.161  encoding stdout as sys.stdout encoding 'UTF-8'
  0.554  Didn't find search plugin
  491.534  return code 0

This doesn't give any sensible information IMHO since apparently the
subprocesses of `bzr viz' don't write any log data into this file,
which is a pity.


    Werner




  reply	other threads:[~2010-01-26 22:07 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
2010-01-26 22:07   ` Werner LEMBERG [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100126.230724.243028555.wl@gnu.org \
    --to=wl@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).