Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

gh-118518: Improve perf docs #118708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 7, 2024
Merged

gh-118518: Improve perf docs #118708

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a314710
gh-118518: Improve perf docs
pablogsal May 7, 2024
50d8e06
Update Doc/howto/perf_profiling.rst
pablogsal May 7, 2024
01c1b35
Apply suggestions from code review
pablogsal May 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Apply suggestions from code review 
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
Co-authored-by: Kerim Kabirov <the.privat33r+gh@pm.me>
  • Loading branch information
@pablogsal @JelleZijlstra @Privat33r-dev
3 people committed May 7, 2024
commit 01c1b35c283131a6ad66b67a83a1e24b3f84c8ea
6 changes: 3 additions & 3 deletions 6 Doc/howto/perf_profiling.rst
View file
Open in desktop
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,8 +225,8 @@ 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
add some custom version numbers including a ``-`` character. This means
Expand Down
Loading
Morty Proxy This is a proxified and sanitized view of the page, visit original site.