Skip to content
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

callgrind output? #3

Open
anntzer opened this issue Sep 5, 2018 · 5 comments · May be fixed by #528
Open

callgrind output? #3

anntzer opened this issue Sep 5, 2018 · 5 comments · May be fixed by #528
Labels
enhancement New feature or request

Comments

@anntzer
Copy link
Contributor

anntzer commented Sep 5, 2018

A suggestion: consider providing profiling output in the callgrind format, as there already exists excellent visualizers (e.g., kcachegrind) for it. (I'm writing this same issue to each and every python profiler project that I run into and that appears interesting :-))

@benfred benfred added the enhancement New feature or request label Sep 5, 2018
@benfred
Copy link
Owner

benfred commented Sep 5, 2018

Great idea! I definitely want to expand the visualization options here, and I think writing out callgrind formatted output should be relatively easy to do

@akeskimo
Copy link

Agreed! Callgrind support would be awesome.

@benfred
Copy link
Owner

benfred commented Sep 11, 2018

Current plan for this is laid out here: rbspy/rbspy#180

@okapies
Copy link

okapies commented Jan 18, 2019

Hi, I'd like to know the progress of this topic.

@SDIdo
Copy link

SDIdo commented Oct 31, 2020

Hi,
any news regarding a compatibility between py-spy and Kcachegrind?

@EpigeneMax EpigeneMax linked a pull request Oct 7, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants