/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/scalability.txt

  • Committer: Martin Pool
  • Date: 2007-05-04 08:46:39 UTC
  • mto: (2483.1.1 jam-integration)
  • mto: This revision was merged to the branch mainline in revision 2484.
  • Revision ID: mbp@sourcefrog.net-20070504084639-8v8mzetmr1y74xer
Rename push/pull back to 'run_hooks' (jameinel)

Reorganize Branch.push into some template methods: public push,
_push_with_bound_branches, and _basic_push.  This fixes the case 
where the destination of push is bound, but the source branch
format doesn't support binding.

Run push and pull hook tests with a local branch that does support binding,
rather than skipping if the branch can't be bound to another of the same
format.

(broken) because the hooks are given the wrong parameters when 
pushing into something bound to a remote branch.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/scalability.txt
1
 
***********
2
 
Scalability
3
 
***********
4
 
 
5
 
bzr needs to scale up very well: projects with tens of thousands of
6
 
commits, tens of thousands of files, and tens of thousands of
7
 
branches.
8
 
 
9
 
We are concerned with both the big-O performance of the design, and
10
 
the multiplicative factors of the implementation.  Both is important.
11
 
 
12
 
For example, darcs, svn and arch use more than one inode per working
13
 
file (pristine, id file, etc).  This is only a constant factor, but
14
 
enough to more than double the space used by a typical tree.  We would
15
 
like to avoid it if we can.
16
 
 
17
 
From a early stage in development the features which do work should be
18
 
tested on large trees.
19
 
 
20