← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/scalability.txt

  • Committer: Aaron Bentley
  • Date: 2005-09-13 02:42:07 UTC
  • mto: (1185.1.16)
  • mto: This revision was merged to the branch mainline in revision 1390.
  • Revision ID: aaron.bentley@utoronto.ca-20050913024207-489d573af4b76c4d
Fixed issues with pull not having a default location after 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