/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/groupcompress-design.txt

  • Committer: Breezy landing bot
  • Author(s): Jelmer Vernooij
  • Date: 2019-06-06 22:22:47 UTC
  • mfrom: (7143.22.4 progressbar-context)
  • Revision ID: breezy.the.bot@gmail.com-20190606222247-muw4nwibuoh9b30u
Use contexts for progress bars where possible.

Merged from https://code.launchpad.net/~jelmer/brz/progressbar-context/+merge/358460

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/groupcompress-design.txt
29
29
 
30
30
Reasonable sizes 'amount read' from remote machines to reconstruct an arbitrary
31
31
text: Reading 5MB for a 100K plain text is not a good trade off. Reading (say)
32
 
500K is probably acceptable. Reading ~100K is ideal. However, its likely that
 
32
500K is probably acceptable. Reading ~100K is ideal. However, it's likely that
33
33
some texts (e.g NEWS versions) can be stored for nearly-no space at all if we
34
34
are willing to have unbounded IO. Profiling to set a good heuristic will be
35
35
important. Also allowing users to choose to optimise for a server environment