bzr pull updates working tree even if nothing changed

[John A Meinel]

I'm trying to debug why bzr pull now takes an eternity, even if there is
nothing to be updated.

One thing I found at the end, is that you always do the merge(), even if
 there were no changes (after waiting forever for "comparing_histories",
it switches and the cpu spikes, I assume because it is testing the
working tree).

I feel like bzr pull without any changes should be a no-op. I guess it
is reasonably fast if the statcache is up-to-date. Also, it might just
be that Robert's integration branch is extra slow for me, because it
seems that bzr pull from a different server is quite a bit faster. The
other server is 2000 miles away behind a cable-modem with a 30KB/s
upload cap, but Rob's is probably halfway across the world, though I
would guess that people.ubuntu.com has a big fat pipe. (my ping is 91ms
to people.ubuntu.com)

When I'm saying it is slow, it is taking 6min to handle the
"comparing_history" portion of the code. That's a pretty long time to be
comparing 2 revision-history files. (In comparison to actually download
the 3 files that matter takes only about 10s).

I tried to do a --profile, and the time seems to be spent in the
meta_store, doing some sort of string operations. (see attached)


John
=:->

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: profile.txt
Url: https://lists.ubuntu.com/archives/bazaar/attachments/20050915/5f06911a/attachment.txt 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050915/5f06911a/attachment.pgp