/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: Vincent Ladeuil
  • Date: 2007-06-26 20:32:49 UTC
  • mto: (2581.1.1 cleanup-runbzr)
  • mto: This revision was merged to the branch mainline in revision 2588.
  • Revision ID: v.ladeuil+lp@free.fr-20070626203249-sqm4afiai5dxofum
Deprecate the varargs syntax and fix the tests.

* bzrlib/tests/__init__.py:
(TestCase.run_bzr): Activate the deprecation warning.
(TestCase.run_bzr_error): Add error_regexes to kwargs or run_bzr
get confused.

* bzrlib/tests/blackbox/test_selftest.py:
(TestRunBzr.test_args): Activate.

* bzrlib/tests/blackbox/test_inventory.py:
(TestInventory.assertInventoryEqual): Build the command from args
if not None.

* bzrlib/tests/blackbox/test_ls.py:
(TestLS.ls_equals): Build the command from args if not None.

* bzrlib/tests/blackbox/test_remove_tree.py:
(TestRemoveTree.test_remove_tree_lightweight_checkout_explicit):
Nice catch, we were calling run_bzr instead of run_bzr_error. This
went unnoticed for some time...

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