/brz/remove-bazaar

To get this branch, use:
bzr branch http://gegoxaren.bato24.eu/bzr/brz/remove-bazaar

« back to all changes in this revision

Viewing changes to doc/developers/planned-change-integration.txt

  • Committer: John Arbash Meinel
  • Date: 2010-08-10 20:03:44 UTC
  • mto: This revision was merged to the branch mainline in revision 5376.
  • Revision ID: john@arbash-meinel.com-20100810200344-6muerwvkafqu7w47
Rework things a bit so the logic can be shared.

It turns out that some of the peak memory is actually during the inventory
to string to bundle translations. So re-use the refcount logic there.
This actually does show a decrease in peak memory.
Specifically 'cd bzr.dev; bzr send ../2.2' drops from 221MB peak to 156MB.

We don't speed anything up (16.5s both ways), but peak memory is quite
a bit better.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/planned-change-integration.txt
73
73
 * Working tree disk ordering: Knowing the expected order for disk operations
74
74
   may influence the needed use case specific APIs, so having a solid
75
75
   understanding of what is optimal - and why - and whether it is pessimal on
76
 
   non linux platforms is rather important.
 
76
   non-Linux-kernel platforms is rather important.
77
77
 
78
78
 * Be able to version files greater than memory in size: This cannot be
79
79
   achieved until all parts of the library which deal with user files are able