Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
Co-authored-by: Kerim Kabirov <the.privat33r+gh@pm.me>
  • Loading branch information
3 people authored May 7, 2024
1 parent 50d8e06 commit 6a3928e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Doc/howto/perf_profiling.rst
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,7 @@ How to work without frame pointers
----------------------------------

If you are working with a Python interpreter that has been compiled without
frame pointers you can still use the ``perf`` profiler but the overhead will be
frame pointers, you can still use the ``perf`` profiler, but the overhead will be
a bit higher because Python needs to generate unwinding information for every
Python function call on the fly. Additionally, ``perf`` will take more time to
process the data because it will need to use the DWARF debugging information to
Expand All @@ -225,7 +225,7 @@ which will enable the JIT mode for the ``perf`` profiler.

Due to a bug in the ``perf`` tool, only ``perf`` versions higher than v6.8
will work with the JIT mode. The fix was also backported to the v6.7.2
version of the tool.
version of the tool.

Note that when checking the version of the ``perf`` tool (which can be done
by running ``perf version``) you must take into account that some distros
Expand Down

0 comments on commit 6a3928e

Please sign in to comment.