[MERGE] optimize annotate

[Aaron Bentley]

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

Wouter van Heyst wrote:
> On Tue, Nov 28, 2006 at 06:05:01PM -0500, Aaron Bentley wrote:
>> 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.
> 
> So what would this do to a 5MB file with 200 versions?

As you suspect, it would fill 1000MB of memory.

It's worth bearing in mind that I'm talking about revisions here, and
they're quite small (1K or so).

If we were retrieving versions of a file, rather than versions of the
revision knit, we'd probably want to take a different approach, like
retrieving batches of 25.

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

iD8DBQFFbMaa0F+nu1YWqI0RAubyAJwNLvfpEw1A/pfQ1FXKlAry75biOQCeIOxh
csEWGMTVl73C2842n+Lnpw4=
=iFPw
-----END PGP SIGNATURE-----