[MERGE] optimize annotate

Aaron Bentley aaron.bentley at utoronto.ca
Tue Nov 28 23:05:01 GMT 2006


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

Wouter van Heyst wrote:
> Even though the sizable amount of annotations is listified first.
> I have trouble seeing when that would become a problem, as so often with
> these kind of tradeoffs.

Knits are delta compressed, so each text 'version' must be built from
older revisions, up to the last fulltext.  If any of the intermediate
versions would be useful in generating another needed version, it's more
efficient to generate both versions at once.  So retrieving multiple
versions of the revision knit at the same time is generally faster than
retrieving the same revisions in multiple steps.

There's also disk-caching advantages.

Retrieving multiple revisions at once is the same strategy I used to
speed up 'log'.  It applies to revision_trees also.

Plus, my code avoids retrieving the same revision twice, which the old
code did not do.

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

iD8DBQFFbMCd0F+nu1YWqI0RAnOKAJwJnD7Vfqkmr1xf2fkaP0mIJBeiewCeMxsU
Sr1xcQ+Gt0MyaZn62tVG7Eo=
=HfGq
-----END PGP SIGNATURE-----




More information about the bazaar mailing list