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
9
We are concerned with both the big-O performance of the design, and
10
the multiplicative factors of the implementation. Both is important.
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.
17
From a early stage in development the features which do work should be
18
tested on large trees.
added
removed
doc/scalability.txt
