[GitHub] [incubator-mxnet] szha commented on issue #15069: [WIP] Profiler RFC: Introducing new APIs

2019-05-30 Thread GitBox
szha commented on issue #15069: [WIP] Profiler RFC: Introducing new APIs URL: https://github.com/apache/incubator-mxnet/issues/15069#issuecomment-497411458 do you feel that aggregating raw profiler dumps is worth adding a new C API? to me, this aggregation doesn't seem like a core

[GitHub] [incubator-mxnet] szha commented on issue #15069: [WIP] Profiler RFC: Introducing new APIs

2019-05-29 Thread GitBox
szha commented on issue #15069: [WIP] Profiler RFC: Introducing new APIs URL: https://github.com/apache/incubator-mxnet/issues/15069#issuecomment-497062410 Yes, and a python script would do that nicely without involving other frontend (or mxnet). For example this one:

[GitHub] [incubator-mxnet] szha commented on issue #15069: [WIP] Profiler RFC: Introducing new APIs

2019-05-29 Thread GitBox
szha commented on issue #15069: [WIP] Profiler RFC: Introducing new APIs URL: https://github.com/apache/incubator-mxnet/issues/15069#issuecomment-497055892 > So instead of adding a utility that parse that table into a JSON string, we can return a JSON string from the backend directly.

[GitHub] [incubator-mxnet] szha commented on issue #15069: [WIP] Profiler RFC: Introducing new APIs

2019-05-28 Thread GitBox
szha commented on issue #15069: [WIP] Profiler RFC: Introducing new APIs URL: https://github.com/apache/incubator-mxnet/issues/15069#issuecomment-496726679 > Why add a new profiler API get_summary() in the back-end rather than a python parser utility that returns in JSON? This is we