You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see the benefit of your proposal. Though I'm not sure how hard it would be to directly generate that profile format. Maybe it would be easier to transform the current format.
I'd be happy to review a patch for that, I'm currently busy finishing up for version 0.4.0.
Hi
There are several problems with callgrind output (the viewer shows cycles).
It's easy to generate the format, I think I have a script somewhere that
converts one to the other (but not sure where)
On Wed, Feb 15, 2017 at 12:12 PM, Richard Plangger ***@***.*** > wrote:
I see the benefit of your proposal. Though I'm not sure how hard it would
be to directly generate that profile format. Maybe it would be easier to
transform the current format.
I'd be happy to review a patch for that, I'm currently busy finishing up
for version 0.4.0.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFPuPgiwC5FmyhIlt-VtOzcunp4t4MFks5rct27gaJpZM4MBS0t>
.
https://github.com/vpelletier/pprofile is a pure python statistical profiler which has (IMO) a main strong feature compared to other profilers: it can output its result directly in callgrind format (https://github.com/vpelletier/pprofile#output), which means that they can be visualized using tools built for that purpose (e.g. kcachegrind, http://kcachegrind.github.io).
Is there any chance a callgrind output format could be added to vmprof?
Thanks in advance.
The text was updated successfully, but these errors were encountered: