bzr st on a working copy is slow

bzr checkouts contain all history locally, svn (lightweight) checkouts do not and therefore contact with the server is required to retrieve some of that information.

I don't think there's much that bzr-svn could be doing differently here.

They do contain enough information for "svn st", don't they?

Yes, but the bzr API requires other stuff as well - the repository layout and file ids, for example.

re-assigning this to bzr, as this is as slow on native bzr lightweight checkouts as on svn lightweight checkouts with the recent svn/bzr-foreign performance improvements.

charis:~/tmp/bzr-lw% time bzr st
bzr st 0.32s user 0.06s system 7% cpu 5.326 total

charis:~/tmp/svn-lw% time ~/bzr/foreign/bzr st
~/bzr/foreign/bzr st 1.43s user 0.34s system 37% cpu 4.722 total

Is this any more than just connecting to the remote machine? (establishing an ssh connection, for example)

At 'bzr st' time, we do make a connection to make sure the target branch exists, etc.

On Mon, Feb 23, 2009 at 05:17:13AM -0000, John A Meinel wrote:
> Is this any more than just connecting to the remote machine?
> (establishing an ssh connection, for example)

> At 'bzr st' time, we do make a connection to make sure the target branch
> exists, etc.
It is just connecting to the remote machine and checking for the
latest revid there.

Cheers,

Jelmer