mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Skalicky, Sam" <sska...@amazon.com.INVALID>
Subject Re: [apache/incubator-mxnet] [RFC] MXNet 2.0 API Deprecation (#17676)
Date Mon, 02 Mar 2020 19:25:39 GMT
TensorRT support is currently using ONNX to convert from NNVM: https://github.com/apache/incubator-mxnet/blob/746cbc55fd666bb4529e88d247fed8e0907270f9/src/operator/subgraph/tensorrt/tensorrt.cc#L313-L318<https://github.com/apache/incubator-mxnet/blob/746cbc55fd666bb4529e88d247fed8e0907270f9/src/operator/subgraph/tensorrt/nnvm_to_onnx-inl.h>

Although I would like to see TensorRT support moved away from ONNX with a native integration
using the Accelerator API compile support: https://github.com/apache/incubator-mxnet/pull/17623.
But the migration from ONNX to AccAPI is still in discussion and the compile support PR is
not merged yet (shameless plug: please review! :-D)

Sam

On Feb 28, 2020, at 9:06 PM, JackieWu <notifications@github.com<mailto:notifications@github.com>>
wrote:

I think we should keep ONNX APIs, since it is able to export many basic models, although it
is not perfect. Users will train their models in MXNet 2.0, and export ONNX model,  then use
the ONNX model in their deployment frameworks. (http://onnx.ai/supported-tools).

It is useful to attract users to use MXNet 2.0 to train their models with ONNX.

--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17676#issuecomment-592878029


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message