[GitHub] cjolivier01 opened a new pull request #8972: Profiling enhancements, python API, vtune and chrome tracing objects, etc.

[GitBox <gi...@apache.org>]

cjolivier01 opened a new pull request #8972: Profiling enhancements, python API, vtune and chrome tracing objects, etc.
URL: https://github.com/apache/incubator-mxnet/pull/8972
 
 
   @piiswrong 
   @tqchen 
   ## Description ##
   
   1. Continuous, asynchronous profile dumping
   
   2. VTune objects: Counter, Task, Event, Frame, Instant-Mark (see screen shot)
     - All available from C++ and python 
     - Equivalents also available in chrome://tracing screen (see screen shot)
     - With Vtune, you get separate call stack paths for events and tasks, including hot spots down to the line of code
   
   3. Memory usage profiling (CPU and GPU)
   
   4. C API Profiling
   
   5. Individual Operator Profiling
   
   6. More granular profiling config (Symbolic ops, All ops, API, Memory, etc)
   
   7. VTune profiling tools
   
   Screen shots:
   
   VTune (note API domain/task grouping, operator task grouping, API and memory counters, etc.)
   ![vtune](https://user-images.githubusercontent.com/11234557/33683094-984f8960-da7e-11e7-8c9e-9bd91a054a5d.png)
   
   Chrome tracing:  (note category/API grouping, operator grouping, API and memory counters, etc.)
   ![chrome_tracing](https://user-images.githubusercontent.com/11234557/33683128-b0ccc9b2-da7e-11e7-98f2-4d121f2f76af.png)
   
   ![zoomchrome](https://user-images.githubusercontent.com/11234557/33686946-579e58e4-da8b-11e7-82c7-d4d797c61fdc.png)
   
   ## Checklist ##
   ### Essentials ###
   - [ ] Passed code style checking (`make lint`)
   - [ ] Changes are complete (i.e. I finished coding on this PR)
   - [ ] All changes have test coverage
   - [ ] For user-facing API changes, API doc string has been updated. For new C++ functions in header files, their functionalities and arguments are well-documented. 
   - [ ] To my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change
   
   ### Changes ###
   - [ ] Feature1, tests, (and when applicable, API doc)
   - [ ] Feature2, tests, (and when applicable, API doc)
   
   ## Comments ##
   - If this change is a backward incompatible change, why must this change be made.
   - Interesting edge cases to note here
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services