2.1.0 bzr performance under Cygwin
Jari Aalto
jari.aalto at cante.net
Sun Mar 14 10:44:55 GMT 2010
John Arbash Meinel <john at arbash-meinel.com> writes:
> Jari Aalto wrote:
>
>> An example:
>>
>>
>> The startup of bzr takes quite a much time for each commands. If there
>> is a way obtain detailed profiling results, let me know how can I help.
>>
>> Jari
>>
>
> The best I've found is to... not use the cygwin version of bzr. Python
> already has higher startup overhead on Windows than on Linux (like 500ms
> vs <100ms to startup bzr on the same hardware), and cygwin just makes
> that a whole lot worse (IIRC >1000ms startup time).
Hm, python startup is quite fast, but commands takes close 3x more:
$ time python -V # real 0m0.208s
$ time bzr --version # real 0m3.250s
$ time hg --version
> I use cygwin as my shell, and the native bzr client, which works almost
> all the time. (It doesn't support ~ expansion, symlinks or the
> executable bit, but those haven't been necessary for me.)
The TILDE, /etc/fstab, symlinks + Emacs + other tools are the reason for
Cygwin's popularity. It enables to use identical environment (bash
aliases, personal functions and all that).
> I certainly wish I could say "do this" and python on cygwin wouldn't be
> so slow. But I've never found any solution for it.
It would be interesting to see if the "service" plugin would help here.
The problem is that it is currenly not usable under Cygwin's Python (old
version).
What about the libraries that Bzr loads? Is there an overhead that could
be reduced? Compare to:
$ time bzr --version # real 0m1.984s
$ time hg --version # real 0m0.594s
$ time bzr init # real 0m2.016s
$ time hg init # real 0m0.750s
Jari
More information about the bazaar
mailing list