samskalicky commented on pull request #18904:
URL: https://github.com/apache/incubator-mxnet/pull/18904#issuecomment-674552661


   > @samskalicky thanks for starting on this! does it supersede the custom c++ 
ops?
   
   No, I think C++ custom ops are still useful for those not familiar with 
MXNet backend or who dont want to build MXNet from source. C++ custom ops are 
the improvement on Python custom ops, easy to write, easy to use, almost as 
fast as built-in ops.
   
   External ops will be for those willing to build MXNet from source, or who 
need to absolute highest performance for the op. In terms of performance we're 
talking about ops with a short compute time (ie. less than 10ms) where the 
overhead of the C++ custom op is not tolerable. For ops with lots of 
computation, the perf will be bounded by the compute and the C++ custom op 
overhead wont be the bottleneck. 
   
   Im working on a project (at some point soon i'll be able to share more 
details) using C++ custom ops for subgraphs, and able to achieve performance 
improvements over built-in MXNet ops. So theres still motivation to keep them 
for their simplicity. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to