[Question] Tracing differences between glow and torch_glow

[Hopobcn]

Glow has a Trace infrastructure well documented here Tracing.md and specified here TraceEvents.h.

Some examples like examples/resnet-runtime.cpp and examples/tracing-compare.cpp define a --trace-path flag to dump all traces to a file after execution. The tool tools/loader/ExecutionCoreHelperFunctions.cpp also defines --trace-path to activate traces but unfortunately on some cases it's not used.

Then torch_glow has enable_glow_tracing / disable_glow_tracing flags to enable tracing, but (apparently) only CachingGraphRunner.cpp respects that flag. JITGraphRunner would remain untraced. Also, the output trace name is not configurable like in the examples/ExecutionCoreHelperFunctions case.

Should I deduce that --trace-path is a non-standard way of activating traces and the only way of activating traces that is part of the public interface would be torch_glow's enable_glow_tracing?