samskalicky commented on issue #17034: [WIP] Dynamic subgraph property URL: https://github.com/apache/incubator-mxnet/pull/17034#issuecomment-565886128 > 1. Can we support implicit using external backends by setting some env variables? That is, can we use `export MXNET_SUBGRAPH_BACKEND=myProp` to enable it without changing scripts? Sure, but I would like to do that as part of a separate PR. I want to have another PR with a set of usability enhancements for external libraries: - Load libraries that are found as siblings next to libmxnet.so/dll. This will allow us to package external libraries into the pip wheel (ie. MKLDNN, TensorRT) - Load libraries that are specified in an environment variable like `MXNET_EXT_LIBS=/path/to/libmylib.so` - (your suggestion) Apply subgraphBackend during bind when specified by an environment variable like `MXNET_SUBGRAPH_BACKEND=myProp` > 2. How to decide which subgraph backends should be integrated as external libraries? For example, we've had MKLDNN and TensorRT as mxnet native supported subgraph backends, what's the next plan for them? And, if we want to add more subgraph backends in future, have it to be integrated as external libraries? What's the release management / policy for such external subgraph backends? I think there are a lot of reasons that it would be good to make MKLDNN and TensorRT external libraries, most important of which would be to let the Intel/Nvidia teams move faster by not being tied down to releases. It would also speed development since compilation would not include all of MXNet, just the library pieces. We can also host external libraries in a bucket and have an API to download/install them (like `mx.test_utils.download()`) then users can pull the latest library whenever there is a new version and dont have to wait for the next MXNet release. But im not looking to pressure anyone to do this now. When the time is right it will make sense to do it. :-)
---------------------------------------------------------------- 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] With regards, Apache Git Services
