From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: vc-print-log vs. bzr log
Date: Sat, 15 Sep 2012 19:36:01 +0200 [thread overview]
Message-ID: <87wqzvb33y.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <83obl7s116.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 15 Sep 2012 19:28:53 +0300")
On Sat, 15 Sep 2012 19:28:53 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: emacs-devel@gnu.org
>> Date: Sat, 15 Sep 2012 18:04:24 +0200
>>
>> Here's a comparison between the shell command with M-!:
>>
>> Sat 2012-09-15 16:46:33 +0200
>> 0.182 bazaar version: 2.5.1
>> 0.182 bzr arguments: [u'log', u'-r-1',
>> u'/data/steve/bzr/emacs/quickfixes/lisp/gnus/gnus-group.el']
>> 0.186 looking for plugins in /home/steve/.bazaar/plugins
>> 0.196 looking for plugins in /usr/lib64/python2.7/site-packages/bzrlib/plugins
>> 0.226 looking for plugins in /usr/lib/python2.7/site-packages/bzrlib/plugins
>> 0.240 encoding stdout as osutils.get_user_encoding() 'utf-8'
>> 0.309 opening working tree '/data/steve/bzr/emacs/quickfixes'
>> 0.417 encoding stdout as osutils.get_user_encoding() 'utf-8'
>> 0.480 return code 0
>>
>> and `C-u C-x v l RET RET' on the same file:
>>
>> Sat 2012-09-15 17:56:19 +0200
>> 0.167 bazaar version: 2.5.1
>> 0.167 bzr arguments: [u'log', u'-l', u'1', u'gnus-group.el']
>> 0.171 looking for plugins in /home/steve/.bazaar/plugins
>> 0.179 looking for plugins in /usr/lib64/python2.7/site-packages/bzrlib/plugins
>> 0.203 looking for plugins in /usr/lib/python2.7/site-packages/bzrlib/plugins
>> 0.211 encoding stdout as osutils.get_user_encoding() 'utf-8'
>> 0.277 opening working tree '/data/steve/bzr/emacs/quickfixes'
>> 0.359 encoding stdout as osutils.get_user_encoding() 'utf-8'
>> 18.561 return code 0
>>
>> What is happening between the last two entries that takes 18 seconds?
>
> That's when bzr does the actual job of accessing the branch meta-data
> and getting the information you asked for.
>
> Do you see the above in "emacs -Q" as well?
Yes, and the difference is even a bit larger:
Sat 2012-09-15 19:21:08 +0200
0.170 bazaar version: 2.5.1
0.171 bzr arguments: [u'log', u'-r-1', u'/data/steve/bzr/emacs/quickfixes/lisp/gnus/gnus-group.el']
0.174 looking for plugins in /home/steve/.bazaar/plugins
0.182 looking for plugins in /usr/lib64/python2.7/site-packages/bzrlib/plugins
0.206 looking for plugins in /usr/lib/python2.7/site-packages/bzrlib/plugins
0.217 encoding stdout as osutils.get_user_encoding() 'utf-8'
0.278 opening working tree '/data/steve/bzr/emacs/quickfixes'
0.367 encoding stdout as osutils.get_user_encoding() 'utf-8'
0.419 return code 0
Sat 2012-09-15 19:21:50 +0200
0.203 bazaar version: 2.5.1
0.203 bzr arguments: [u'log', u'-l', u'1', u'gnus-group.el']
0.207 looking for plugins in /home/steve/.bazaar/plugins
0.215 looking for plugins in /usr/lib64/python2.7/site-packages/bzrlib/plugins
0.239 looking for plugins in /usr/lib/python2.7/site-packages/bzrlib/plugins
0.247 encoding stdout as osutils.get_user_encoding() 'utf-8'
0.309 opening working tree '/data/steve/bzr/emacs/quickfixes'
0.395 encoding stdout as osutils.get_user_encoding() 'utf-8'
19.272 return code 0
> What do you see in ~/.bzr.log if you invoke
>
> bzr log -l1 gnus-group.el
>
> from the shell prompt?
Sat 2012-09-15 19:26:14 +0200
0.127 bazaar version: 2.5.1
0.127 bzr arguments: [u'log', u'-l1', u'gnus-group.el']
0.131 looking for plugins in /home/steve/.bazaar/plugins
0.139 looking for plugins in /usr/lib64/python2.7/site-packages/bzrlib/plugins
0.163 looking for plugins in /usr/lib/python2.7/site-packages/bzrlib/plugins
0.171 encoding stdout as sys.stdout encoding 'UTF-8'
0.228 opening working tree '/data/steve/bzr/emacs/quickfixes'
0.312 encoding stdout as sys.stdout encoding 'UTF-8'
18.968 Transferred: 0kB (0.0kB/s r:0kB w:0kB)
18.968 return code 0
> If you see the same 18 sec, does it help to
> say
>
> bzr --no-plugins log -l1 gnus-group.el
>
> instead?
No, it's even worse:
Sat 2012-09-15 19:26:56 +0200
0.155 bazaar version: 2.5.1
0.155 bzr arguments: [u'--no-plugins', u'log', u'-l1', u'gnus-group.el']
0.168 encoding stdout as sys.stdout encoding 'UTF-8'
0.243 opening working tree '/data/steve/bzr/emacs/quickfixes'
0.328 encoding stdout as sys.stdout encoding 'UTF-8'
19.122 Transferred: 0kB (0.0kB/s r:0kB w:0kB)
19.122 return code 0
In any case, obviously this is a bzr issue, not an Emacs one. Or can we
make VC also get the quicker bzr -r-1 results?
Steve Berman
next prev parent reply other threads:[~2012-09-15 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 13:07 vc-print-log vs. bzr log Stephen Berman
2012-09-15 13:37 ` Andreas Schwab
2012-09-15 14:56 ` Stephen Berman
2012-09-15 15:45 ` Eli Zaretskii
2012-09-15 16:04 ` Stephen Berman
2012-09-15 16:28 ` Eli Zaretskii
2012-09-15 17:36 ` Stephen Berman [this message]
2012-09-15 17:56 ` Andreas Schwab
2012-09-15 19:36 ` Eli Zaretskii
2012-09-15 13:51 ` 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=87wqzvb33y.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--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).