From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: `bzr viz' slooow Date: Wed, 27 Jan 2010 06:11:58 +0200 Message-ID: <83my00425t.fsf@gnu.org> References: <20100126.180554.173876640.wl@gnu.org> <83eilc69kw.fsf@gnu.org> <20100126.230724.243028555.wl@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1264565602 18605 80.91.229.12 (27 Jan 2010 04:13:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 27 Jan 2010 04:13:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: Werner LEMBERG Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 27 05:13:14 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NZzGg-000350-M6 for ged-emacs-devel@m.gmane.org; Wed, 27 Jan 2010 05:12:38 +0100 Original-Received: from localhost ([127.0.0.1]:39895 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZzGh-0004Q8-Kr for ged-emacs-devel@m.gmane.org; Tue, 26 Jan 2010 23:12:39 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NZzGd-0004Pk-A3 for emacs-devel@gnu.org; Tue, 26 Jan 2010 23:12:35 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NZzGY-0004P1-Nt for emacs-devel@gnu.org; Tue, 26 Jan 2010 23:12:34 -0500 Original-Received: from [199.232.76.173] (port=59551 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZzGY-0004Ox-IL for emacs-devel@gnu.org; Tue, 26 Jan 2010 23:12:30 -0500 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:33639) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NZzGW-0001To-8f; Tue, 26 Jan 2010 23:12:28 -0500 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0KWW009000SCHR00@a-mtaout22.012.net.il>; Wed, 27 Jan 2010 06:11:58 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([77.127.180.161]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KWW007CE0ZTTO80@a-mtaout22.012.net.il>; Wed, 27 Jan 2010 06:11:54 +0200 (IST) In-reply-to: <20100126.230724.243028555.wl@gnu.org> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:120477 Archived-At: > Date: Tue, 26 Jan 2010 23:07:24 +0100 (CET) > Cc: emacs-devel@gnu.org > From: Werner LEMBERG > > >> 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? With "bzr info", if with nothing else, like you did. > > 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. Yes, a pity. So my guess would be that "bzr viz" tries to produce the full DAG of the branch history, which is expensive. Does it have any options equivalent to the -n option of "log", which limits the depth of the graph?