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.

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

Already on GitHub? Sign in to your account

Profile Native Extensions #2

Open
benfred opened this Issue Aug 22, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@benfred
Owner

benfred commented Aug 22, 2018

Right now we are figuring out the call stack of the Python program by inspecting the PyInterpreterState/PyThreadState/PyFrameObject variables found in the target python program. This means we don't get information about time spent in non-python threads and time spent in native extensions to python (like extension code written in Cython or C++)

It could be useful to profile these native extensions in addition to the Python call stacks. It might be possible to use something like libunwind to augment the Python call stack to get this information.

@benfred benfred added the enhancement label Aug 22, 2018

@anntzer

This comment has been minimized.

Show comment
Hide comment
@anntzer

anntzer Sep 5, 2018

You may(?) want to compare with https://github.com/vmprof/vmprof-python, which also uses libunwind.

anntzer commented Sep 5, 2018

You may(?) want to compare with https://github.com/vmprof/vmprof-python, which also uses libunwind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment