-
Notifications
You must be signed in to change notification settings - Fork 355
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
TinyProfiler: output in JSON format #3904
Comments
If this is a feature that would be considered merge-able, I could prototype this given a few pointers on where to start in the profiler code. |
Yes, that would be great. For TinyProfiler, the output is done in TinyProfiler::PrintStats. You can modify it to additionally output the results in a separate file. |
I've moved the BLProfiler trace output to a separate issue: #3916. |
@BenWibking - Closing this issue due to lack of activity. Please re-open it if there is still a problem. |
The built-in profiler provides very useful data, but it is difficult to perform in-depth analysis with Python scripts.
It would be very useful if the profiler could also output its results in Caliper's JSON (https://software.llnl.gov/Caliper/OutputFormats.html#json-split) or JSON-split (https://software.llnl.gov/Caliper/OutputFormats.html#json-split) format.
These are formats that Hatchet (https://github.com/LLNL/hatchet) could read and turn into Pandas DataFrames.
The text was updated successfully, but these errors were encountered: