Expensive plugins

John Arbash Meinel john at arbash-meinel.com
Tue Jun 1 16:04:27 BST 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gary van der Merwe wrote:
> On 01/06/10 15:50, Gary van der Merwe wrote:
>> I wrote script to do
>> $ export BZR_DISABLE_PLUGINS=[all other plugins]
>> $ time bzr rocks
>> for each plugin that I have installed on my desktop, then take the real
>> time for each of those and subtract a baseline time bzr rocks --no-plugins
>>
> <snip>
>> Needless to say, I'm going to look into why qbzr is the worst....
> 
> Martin GZ suggested testing from cold caches, so running
> 
> sudo sync
> sudo echo 3 | sudo tee /proc/sys/vm/drop_caches
> 
> before each test, the results are:

Just to mention, a more valid test is to run "bzr status" (in an minimal
working tree) for this.

It is interesting to see what plugins import, but honestly, it isn't
very representative of what overhead they actually introduce versus
day-to-day tasks.

For example, I'm pretty sure "from bzrlib import branch" is expensive,
bet you have to do it to get any real work done. So I don't think
plugins that use it need to go to excessive contortions to avoid it.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwFIXsACgkQJdeBCYSNAANz9ACgwLbT7XkPlNVOo+HpE0hgG92V
+PcAoLHCb8s1unV6NndULWy1faa0DOKQ
=dVjR
-----END PGP SIGNATURE-----



More information about the bazaar mailing list