You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mxnet.apache.org by GitBox <gi...@apache.org> on 2020/11/10 20:49:29 UTC

[GitHub] [incubator-mxnet] mk-61 commented on issue #18697: AMP for mx2

mk-61 commented on issue #18697:
URL: https://github.com/apache/incubator-mxnet/issues/18697#issuecomment-724958074


   Hi @szha, why do you want to implement AMP with a graph pass? Which aspects of the current approach do you expect to improve by switching to a graph pass?
   One drawback of the Python-side monkey patching I see is that it is sensitive to how various ops are registered on the client side - NumPy vs legacy, imperative vs hybridized, etc. - ideally, we want to handle this in a uniform way, since we don't really care about these distinctions, as far as AMP itself is concerned.
   But I am curious if you have some other deficiencies of the current approach in mind.


----------------------------------------------------------------
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@mxnet.apache.org
For additional commands, e-mail: issues-help@mxnet.apache.org