commit performance regression in 0.11

[Aaron Bentley]

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

Robert Collins wrote:
>> Yes, I realize that it will be a performance
>> advantage
>> for dirstate, once it arrives, but right now it's a disadvantage.
> 
> It can be an advantage right now though, which is why we should do this.

How can it be an advantage right now?  By caching the basis inventory on
commit?

> Consider a bzr working tree committing to a svn one, or a bzr working
> tree that is a checkout of an hg one. Yes these are not our primary use
> cases, but thinking about them is a good way of ensuring we can justify
> any coupling that we do do.

Anything that is a repository is expected to implement
get_inventory_xml.  If it's hg or svn, I bet it will return one of our
inventory formats.

> working trees should be orthogonal to the repository format, which means
> that they should have constraints on them placed on them by bzr's model,
> not by any one repository.

I'm not saying it has to be a hard link.  It can be a hint about which
inventory format will perform best.  Anyhow, that's one of several options.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFGFJ50F+nu1YWqI0RAtUoAKCAa0913amr0L12UvitHrha0DT/jgCgg3RV
mH8kGiGCYz9TNXxng+jZok4=
=OLYp
-----END PGP SIGNATURE-----