← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

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

  • Committer: John Arbash Meinel
  • Date: 2007-11-30 05:08:02 UTC
  • mfrom: (2951.2.10 reconcile.packs)
  • mto: This revision was merged to the branch mainline in revision 3063.
  • Revision ID: john@arbash-meinel.com-20071130050802-aqswmc0a7sv7hal9
merge Robert's reconcile work.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/performance-contributing.txt
11
11
pointing at it that is also BLUE, and start working on that.
12
12
 
13
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
 
14
flag. For instance running ``bzr -Devil commit -m "test"`` will log a backtrace
15
15
to the bzr log file for every method call which triggers a slow or non-scalable
16
16
part of the bzr library. So checking that a given command with ``-Devil`` has
17
17
no backtraces logged to the log file is a good way to find problem function