-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[MXNET-367] update mkldnn to v0.14 and disable building test examples #10736
Conversation
Looks good to me. But I guess there will be some issues need to fix. MKL-DNN added some new formats which are not handled in mxnet. Let's wait for ci finishing. |
also looks good to me. We should always attach to the official release from now on. How often do you have a release? |
Seems CI is still using b4137df:
=========== |
@TaoLv mxnet has been using latest master branch of mkldnn, which means it already has v0.14. i believe v0.14 comes with several performance enhancements and features. We could go back to v0.13 , but since mxnet has been using master branch, i think we should just go with v0.14. |
@ashokei No, we are not using v0.14. We are using commit b4137df, which was submitted to mkldnn repo at Mar 20. |
@TaoLv you are right, this is hardcoded somewhere, we can update to fixed release tag (may be v0.13) until v0.14 is verified with mxnet. I will look into it. |
Yes. I agree that release always means better stability than latest commit in master branch. But I have the same concern with @zheng-da , what's the release period of mkl-dnn? If mkl-dnn has a hot-fix in their master branch, then what should we do? Seems mkldnn team would not release a new version for a hot-fix. Regarding to other 3rdparty packages, they are pointed to the specific version in the same way of mkl-dnn, a specific commit id, not a release tag. |
actually, why do we not move the mkldnn submodule to the certain commit associated with the release directly? i think it's better than checking the mkldnn release out explicitly in the script. |
yes, we could just update submodule to v0.14, i made the changes. @TaoLv mkl-dnn releases are probably more thoroughly tested than just some random commit, we should at the minimum track latest mkldnn release (currently v0.14), and we could change to hot fix as needed (until v0.15 comes out). |
OK. I agree to change to current commid id b4137df to v0.14's 0e7ca73. Since we always need submit PR and pass ci to update the commid id, I think there shouldn't have any functional issues by this approach. So we don't need wait for next release to resolve some bugs or adding some new features. Commit from master branch should be OK to be a dependency of mxnet, same as other 3rdparty dependencies. |
Could you update all locations of MKLDNN to 0.14? We have different scripts like cmake downloading mkl on the fly and we should check that they are all on-par |
mark don't forget windows when #10629 is merge |
@marcoabreu updated all locations, can you please merge if ok. thanks. |
@@ -58,16 +58,16 @@ MXNET_ROOT=`dirname $0` | |||
USE_MKLML=0 | |||
# NOTE: if you update the following line, please also update the dockerfile at | |||
# tests/ci_build/Dockerfile.mkl | |||
VERSION_MATCH=20171227 | |||
VERSION_MATCH=20180406 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this version is tied to the specific mkldnn commit, should this script live in mkldnn instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this script can be used independent of mkldnn (for eg: mshadow with mklml blas api)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't seen such use before. Has this been added as an option to USE_BLAS flag?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
USE_MKLML
is used inside mshadow build. USE_BLAS can be set to mkl
.
wget --no-check-certificate -O /tmp/mklml.tgz https://github.com/intel/mkl-dnn/releases/download/v0.14/mklml_lnx_2018.0.3.20180406.tgz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any way to automatically get this from 3rdparty/mkldnn? and this should really be managed by mkldnn because mxnet shouldn't need to directly depend on mklml.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i notice these scripts are called only for docker, as part of docker image build; i think we do not have 3rdparty/mkldnn folder yet , as the actual mxnet build happens later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well our dockerfiles even depend on Caffe, so that topic is already pretty over the top :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marcoabreu can you merge if ok. let me know if any other concern(s).
…apache#10736) * update mkldnn to v0.14 and disable building test examples * update mkldnn to v0.14 release * use git submodule tagging for mkldnn * update mklml to latest version
…examples (apache#10736)" (apache#10808) This reverts commit 3c7afcc.
…apache#10736) * update mkldnn to v0.14 and disable building test examples * update mkldnn to v0.14 release * use git submodule tagging for mkldnn * update mklml to latest version
…examples (apache#10736)" (apache#10808) This reverts commit 3c7afcc.
…apache#10736) * update mkldnn to v0.14 and disable building test examples * update mkldnn to v0.14 release * use git submodule tagging for mkldnn * update mklml to latest version
…examples (apache#10736)" (apache#10808) This reverts commit 3c7afcc.
…apache#10736) * update mkldnn to v0.14 and disable building test examples * update mkldnn to v0.14 release * use git submodule tagging for mkldnn * update mklml to latest version
…examples (apache#10736)" (apache#10808) This reverts commit 3c7afcc.
Description
updated mkldnn submodule to latest release version, and disabled unnecessary build steps for mkldnn-examples/test
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.
Changes
Comments