Comment 15 for bug 405251

> The number of these lines indicates that there's either a lot of revisions (possibly merged revisions),
> a lot of new file versions, or both.
Ok, I'm attaching here the log for the revisions that were added in this pull as displayed by bzr log -n0 --verbose -r1344..1346 (which are the new revisions). I edited out the email adresses 8-/. This was not a large merge in my view, and it most certainly did NOT contain large files. But an earlier commit did (see above; the ones in the CSharpProjects dir)! But these WERE already present in that repo! So it would seem that the code selects something like all revisions, not just the new ones.
The only thing "out of the ordinary" for this merge was that it contained a manual fix for another bazaar bug where it merged incorrectly (reported as bug 405301). This is probably unrelated but at least you know (yesterday was a very bad day as far as Bazaar bugs are concerned 8-/).

> for such large streams it's pretty common for this to take a couple of minutes.
I am not certain what you mean here? You should know that this is an existing repo which has not grown that much in size and has been used for over a year now; and most operations have always been very fast on it (without large data transfers). I noticed the large transfers when upgrading to 1.16, and that was also the version where all other commands got very, very slow.
It looks to me that "the stream is large" because something is wrong in the process which determines which new revisions are needed perhaps?

#14: Please remember that I AM using 1.17. My colleagues are using 1.16 and have much the same problems; but the logs and data you see here are 1.17.