Opened 5 years ago

Last modified 5 years ago

#9419 new feature request

Machine-readable output for profiling

Reported by: ezyang Owned by: ezyang
Priority: normal Milestone:
Component: Profiling Version: 7.9
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:


We'll control whether or not machine-readable output is used using the --machine-readable flag currently used for GC stats.

The format should also be self-explanatory for cost-center stats: per cost center we output the a CSV of cc->time_ticks, cc->mem_alloc. I'm a little less sure how to format the hierarchical cost center stacks; we could print out the entire trace of the stack, or maybe even organize the data recursively from the get go (outputting something JSON like, in that case.)

Change History (2)

comment:1 Changed 5 years ago by ezyang

Differential Rev(s): D124

comment:2 Changed 5 years ago by ezyang

Differential Rev(s): D124
Note: See TracTickets for help on using tickets.