Changes between Version 10 and Version 11 of Profiling
- Timestamp:
- 01/09/13 09:33:31 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Profiling
v10 v11 38 38 === Using pycallgraph to identify bottlenecks == 39 39 General rules and guidelines: 40 * beware that changing the include and exclude sets can have a very noticeable impact on tracing performance, so bear that in mind when making comparisons 40 * beware that changing the include and exclude sets can have a very noticeable impact on performance, so bear that in mind when making comparisons 41 * since the profiling code affects the performance characteristics of the software, once a problem is reasonably well isolated it is often better to switch to dedicated performance monitoring code (using simple print statements for example) 41 42 * start with a small delay (ie: {{{-d 2}}}) to skip the initial setup, potentially longer if you start a server and then also need to connect the client before profiling 42 43 * if testing locally (which is generally more convenient), don't forget to turn off mmap with {{{--no-mmap}}}