← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/developers/performance-contributing.txt

Rather use assertRaises in test_changes_from_with_require_versioned

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/performance-contributing.txt
10
10
changes. In general, pick a BLUE node from performance.png which has nothing
11
11
pointing at it that is also BLUE, and start working on that.
12
12
 
13
 
Adhoc performance work can also be done. One useful tool is the 'evil' debug
14
 
flag. For instance running ``bzr -Devil commit -m "test"`` will log a backtrace
15
 
to the bzr log file for every method call which triggers a slow or non-scalable
16
 
part of the bzr library. So checking that a given command with ``-Devil`` has
17
 
no backtraces logged to the log file is a good way to find problem function
18
 
calls that might be nested deep in the code base.
19
 
 
20
13
Status
21
14
------
22
15