From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Martin Pool" Newsgroups: gmane.emacs.devel Subject: Re: Emacs Bazaar repository Date: Fri, 14 Mar 2008 14:03:17 +1100 Message-ID: References: <87skyvse7k.fsf@xmission.com> <87fxuvl0gi.fsf@offby1.atm01.sea.blarg.net> <87bq5j19ok.fsf@workhorse.earlhome> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1205468559 4775 80.91.229.12 (14 Mar 2008 04:22:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 14 Mar 2008 04:22:39 +0000 (UTC) Cc: Jonathan Lange , Jason Earl , emacs-devel@gnu.org To: dhruva Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 14 05:23:07 2008 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 1Ja1Rj-0003wV-1p for ged-emacs-devel@m.gmane.org; Fri, 14 Mar 2008 05:23:07 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ja1R9-0006td-MF for ged-emacs-devel@m.gmane.org; Fri, 14 Mar 2008 00:22:31 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ja0CX-00077U-3M for emacs-devel@gnu.org; Thu, 13 Mar 2008 23:03:21 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ja0CW-00076f-HO for emacs-devel@gnu.org; Thu, 13 Mar 2008 23:03:20 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ja0CV-00076X-WC for emacs-devel@gnu.org; Thu, 13 Mar 2008 23:03:20 -0400 Original-Received: from wf-out-1314.google.com ([209.85.200.170]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ja0CV-0007ng-JZ for emacs-devel@gnu.org; Thu, 13 Mar 2008 23:03:19 -0400 Original-Received: by wf-out-1314.google.com with SMTP id 29so3727563wff.24 for ; Thu, 13 Mar 2008 20:03:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=HfHYIx/jbPKiB9UBTha2AugUHjz64fnEyUye+XzPuWQ=; b=acuG1ebJzfrXNhgqfSt6mlC+CE5rcL/S/44kv2hc9AsRnYqxvyfwleTnhDqRIrIIf0/F7/vwnthwV1SfjMwcXyakhzuXrio9MaajMElaXJBXTkloq1YdpYKgtHaQp7K9KSfienbkkyE5H7JAGuifi61fJ2jjZ+ESxRn+2gIND3I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=acVLwWNV3dXGwsvW2TH5S5Mao4oGWxLxE9DL6rzBEnGUkdTP+1RPQWyeaHpuaJEZDYyTSbPToi+SnHNi+nIJhID9A49rsFtt2DD+9KW2TyBfcWgoAHRO22uCxWYTZDLzzM0NiPO7qPVqEiXNNc9W96P84IdGp75p6zRNFNWgahQ= Original-Received: by 10.143.40.18 with SMTP id s18mr4737217wfj.156.1205463797502; Thu, 13 Mar 2008 20:03:17 -0700 (PDT) Original-Received: by 10.142.157.3 with HTTP; Thu, 13 Mar 2008 20:03:17 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-Google-Sender-Auth: ce03c629d2eee6ec X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-Mailman-Approved-At: Fri, 14 Mar 2008 00:21:47 -0400 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:92483 Archived-At: On 14/03/2008, dhruva wrote: > On Fri, Mar 14, 2008 at 5:16 AM, Jonathan Lange wrote: > > Definitely. I hate waiting for anything, computers most of all. I'll > > hassle Martin and try to get this fixed. Alternatively, the Bazaar > > project welcomes patches with open arms. :) > > For starters, could anyone please suggest if there is some magic flag > to profile the bzr code? If I can get the time spent in each function > (PYTHON), we would be able to track the real hot spots. I am open to > help in debugging with my current limited knowledge of bzr internals. That would be great, see http://doc.bazaar-vcs.org/bzr.dev/developers/profiling.html and http://doc.bazaar-vcs.org/bzr.dev/en/developer-guide/HACKING.html I believe the main problem is that we are processing the whole graph to work out which revisions merged which others. (which hg and git do not do, iiuc.) For even quite active trees this is good, but emacs has a lot of history. In this case you probably just want the last ten direct commits, bzr log --line -l10. mwh posted a patch to improve this and there is some more that can be done. -- Martin