You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mxnet.apache.org by Steffen Rochel <st...@gmail.com> on 2018/03/09 13:28:41 UTC
call for contributions to next MXNet release
Hi - I would like to propose the next MXNet release.
Initial draft content is listed at MXNet wiki
<https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+next+MXNet+Release>.
I would like to call to all contributors to add features you are working on
and would like to see included in the release. Suggested code freeze is
March 30th with target release by mid April.
Anirudh Subramanian and Chris Olivier have volunteered to co-manage the
release.
Mark your date: we are planing public meetup on Apr 24th in Seattle.
Details to follow.
Regards,
Steffen
Re: call for contributions to next MXNet release
Posted by Steffen Rochel <st...@gmail.com>.
Hi Anirudh - just to clarify - April 9th as target to create 1st release
candidate to start voting process. Suggest to focus between feature freeze
on March 30th and 1st release candidate on April 9th to address the long
list of known bugs - https://github.com/apache/incubator-mxnet/labels/Bug
Regards,
Steffen
On Thu, Mar 15, 2018 at 5:24 PM Anirudh <an...@gmail.com> wrote:
> Hi all,
>
> Chris and I will be working on the 1.2.0 release. If you haven't already,
> please let me know if you have any new features that you are working on and
> would like
> to be included in the release.
>
> <https://cwiki.apache.org/confluence/display/MXNET/
> Project+Proposals+for+next+MXNet+Release>
>
> The plan is to do the code freeze by March 30th with target release date
> of April 9th.
>
> Feel free to add any other comments/suggestions.
>
>
> Anirudh
>
>
> On Wed, Mar 14, 2018 at 6:09 AM, Pedro Larroy <
> pedro.larroy.lists@gmail.com>
> wrote:
>
> > Hi Patric
> >
> > Does it make sense to add instructions to link against mkl in the install
> > docs?
> >
> > For example in OSX you can use MKL by downloading
> > https://github.com/intel/mkl-dnn/releases and adding MKL_RT_LIBRARY and
> > MKL_INCLUDE_DIR plus -DUSE_MKL_IF_AVAILABLE=ON -DUSE_MKLML_MKL=ON
> > -DUSE_MKLDNN=ON
> >
> > This is not documented in the website.
> >
> > What's the performance increase of using MKL in osx when running in CPU
> > mode?
> >
> > Pedro
> >
> > On Wed, Mar 14, 2018 at 1:54 PM, Zhao, Patric <pa...@intel.com>
> > wrote:
> >
> > > My fault, typo for your name, Larroy :(
> > >
> > > > -----Original Message-----
> > > > From: Zhao, Patric [mailto:patric.zhao@intel.com]
> > > > Sent: Wednesday, March 14, 2018 8:40 PM
> > > > To: dev@mxnet.incubator.apache.org; Huang, Jin1 <
> jin1.huang@intel.com>
> > > > Subject: RE: call for contributions to next MXNet release
> > > >
> > > > Thanks, Larryo.
> > > >
> > > > This is a PR to fix this issue, https://github.com/apache/incubator-
> > > > mxnet/pull/10075
> > > > The issue will be gone after this PR is merged.
> > > >
> > > > For the whole logic, we are investigating now and maybe propose a new
> > > > approach for Makefile and CMake.
> > > >
> > > > > -----Original Message-----
> > > > > From: Pedro Larroy [mailto:pedro.larroy.lists@gmail.com]
> > > > > Sent: Wednesday, March 14, 2018 8:31 PM
> > > > > To: dev@mxnet.incubator.apache.org
> > > > > Subject: Re: call for contributions to next MXNet release
> > > > >
> > > > > Hi
> > > > >
> > > > > Can you please fix the build logic?
> > > > > https://github.com/apache/incubator-
> > > > > mxnet/blob/master/CMakeLists.txt#L158
> > > > >
> > > > > https://github.com/apache/incubator-mxnet/issues/10072
> > > > >
> > > > > It wrongly assumes that you have MKL installed, MKLDNN needs to
> check
> > > > > if MKL is available before, or be disabled by default, also in non
> > > intel
> > > > platforms.
> > > > >
> > > > > Pedro
> > > > >
> > > > > On Sun, Mar 11, 2018 at 2:43 PM, Zhao, Patric <
> patric.zhao@intel.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Steffen, really thanks for the helps and I totally agree with you
> > > > > > and Marco's suggestions.
> > > > > > I will summarize the open issues and status for the review soon.
> > > > > >
> > > > > > > What is your github handle?
> > > > > > Github ID: Patric Zhao, https://github.com/pengzhao-intel/
> Da
> > > Zheng,
> > > > > > https://github.com/zheng-da/
> > > > > >
> > > > > > > - do you have design docs we can link to? Does the doc cover
> > > > > > > packaging,
> > > > > > use
> > > > > > > of MXNet with full MKL (I understand there are license issues,
> > but
> > > > > > > we do
> > > > > > have
> > > > > > > users who are or plan to use MXNet with the complete MKL
> package,
> > > > > > > not
> > > > > > just
> > > > > > > DNN subset)?
> > > > > > Design doc: https://cwiki.apache.org/
> > confluence/display/MXNET/The+
> > > > > > design+of+MKLDNN+integration
> > > > > > It's a good suggestion for the full MKL package and we will add
> the
> > > > > > related part in the doc.
> > > > > >
> > > > > > > - do you have performance measurements (or plan to measure) to
> > > > > > > include in release notes?
> > > > > > Yes, we have tested the performance on all C4/C5 instances
> > > > > > (8x,4x,2x,xlarge,large). And the accuracy are verified as well.
> > > > > > We plan to publish these data both in the release note and mxnet
> > > > > > website ( https://mxnet.incubator.apache.org/faq/perf.html).
> > > > > >
> > > > > > > - should we talk about the package at the Apr 24th meetup in
> > > Seattle?
> > > > > > We're based in Shanghai, China; so maybe @Da Zheng?
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > > > > Sent: Sunday, March 11, 2018 6:11 PM
> > > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > > Cc: marco.g.abreu@googlemail.com
> > > > > > > Subject: Re: call for contributions to next MXNet release
> > > > > > >
> > > > > > > Patric - added MKL-DNN to the project list. What is your github
> > > handle?
> > > > > > > I do agree with Marco that we need to resolve disable tests,
> > > > > > > broken
> > > > > > features
> > > > > > > etc. Jira looks like the right answer to create a list of known
> > > issues.
> > > > > > > Questions I do have:
> > > > > > > - do you have design docs we can link to? Does the doc cover
> > > > > > > packaging,
> > > > > > use
> > > > > > > of MXNet with full MKL (I understand there are license issues,
> > but
> > > > > > > we do
> > > > > > have
> > > > > > > users who are or plan to use MXNet with the complete MKL
> package,
> > > > > > > not
> > > > > > just
> > > > > > > DNN subset)?
> > > > > > > - do you have performance measurements (or plan to measure) to
> > > > > > > include in release notes?
> > > > > > > - should we talk about the package at the Apr 24th meetup in
> > > Seattle?
> > > > > > >
> > > > > > > Steffen
> > > > > > >
> > > > > > > On Sat, Mar 10, 2018 at 4:40 AM Zhao, Patric
> > > > > > > <pa...@intel.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Marco,
> > > > > > > >
> > > > > > > > Thanks for the inputs.
> > > > > > > >
> > > > > > > > MKL-DNN is just merged to the master branch in a month. I
> agree
> > > > > > > > that it's not very mature.
> > > > > > > > But, in my mind, there're NO major issues in the current
> > > > > > implementation.
> > > > > > > >
> > > > > > > > The previous data race (flaky test) issue is fixed by Zheng
> Da.
> > > > > > > > We have submitted the PRs to fix the building issues and
> setup
> > > > > > > > Clang CI environment, such as in OSX and Cmake.
> > > > > > > > Meanwhile, we are actively working on the MXNET for the
> > > > > > > > performance, functionality and usability improvements.
> > > > > > > >
> > > > > > > > More positively, I think we should summarize the open issues,
> > > > > > > > and we can focus on these issues you've mentioned.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > >
> > > > > > > > --Patric
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Marco de Abreu [mailto:marco.g.abreu@googlemail.com]
> > > > > > > > > Sent: Saturday, March 10, 2018 9:36 AM
> > > > > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > > > > Subject: Re: call for contributions to next MXNet release
> > > > > > > > >
> > > > > > > > > Hello Patric,
> > > > > > > > >
> > > > > > > > > please be aware of the fact that there are still a lot of
> > > > > > > > > disabled
> > > > > > > > tests, open
> > > > > > > > > MKLDNN issues, broken features and flaky tests that have
> not
> > > > > > > > > been addressed yet. We agreed on merging MKLDNN for the
> time
> > > > > > > > > being to allow broad testing and that we will revisit the
> > > > > > > > > state a bit before the next
> > > > > > > > release.
> > > > > > > > > At the moment, I'd not be in favour of having MKLDNN being
> > > > > > > > > part of
> > > > > > it.
> > > > > > > > >
> > > > > > > > > Best regards,
> > > > > > > > > Marco
> > > > > > > > >
> > > > > > > > > Zhao, Patric <pa...@intel.com> schrieb am Sa., 10.
> > März
> > > > > > > > > 2018,
> > > > > > > > 02:30:
> > > > > > > > >
> > > > > > > > > > Hi Steffen,
> > > > > > > > > >
> > > > > > > > > > We'd like the MKL-DNN backend can be included in the next
> > > > release.
> > > > > > > > > >
> > > > > > > > > > We (Intel engineers) and Zheng-Da (AWS engineer) can
> work
> > > on it.
> > > > > > > > > >
> > > > > > > > > > Could you help add the item in the table?
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > >
> > > > > > > > > > --Patric
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > > > > > > > > Sent: Friday, March 9, 2018 9:29 PM
> > > > > > > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > > > > > > Subject: call for contributions to next MXNet release
> > > > > > > > > > >
> > > > > > > > > > > Hi - I would like to propose the next MXNet release.
> > > > > > > > > > > Initial draft content is listed at MXNet wiki
> > > > > > > > > > > <https://cwiki.apache.org/confluence/display/MXNET/
> > Project
> > > > > > > > > > > +P
> > > > > > > > > > > ropo
> > > > > > > > > > > sals
> > > > > > > > > > > +fo
> > > > > > > > > > > r+next+MXNet+Release>.
> > > > > > > > > > > I would like to call to all contributors to add
> features
> > > > > > > > > > > you are working
> > > > > > > > > > on and
> > > > > > > > > > > would like to see included in the release. Suggested
> code
> > > > > > > > > > > freeze is March 30th with target release by mid April.
> > > > > > > > > > >
> > > > > > > > > > > Anirudh Subramanian and Chris Olivier have volunteered
> to
> > > > > > > > > > > co-manage the release.
> > > > > > > > > > >
> > > > > > > > > > > Mark your date: we are planing public meetup on Apr
> 24th
> > > > > > > > > > > in
> > > > > > Seattle.
> > > > > > > > > > > Details to follow.
> > > > > > > > > > >
> > > > > > > > > > > Regards,
> > > > > > > > > > > Steffen
> > > > > > > > > >
> > > > > > > >
> > > > > >
> > >
> >
>
Re: call for contributions to next MXNet release
Posted by Anirudh <an...@gmail.com>.
Hi all,
Chris and I will be working on the 1.2.0 release. If you haven't already,
please let me know if you have any new features that you are working on and
would like
to be included in the release.
<https://cwiki.apache.org/confluence/display/MXNET/
Project+Proposals+for+next+MXNet+Release>
The plan is to do the code freeze by March 30th with target release date
of April 9th.
Feel free to add any other comments/suggestions.
Anirudh
On Wed, Mar 14, 2018 at 6:09 AM, Pedro Larroy <pe...@gmail.com>
wrote:
> Hi Patric
>
> Does it make sense to add instructions to link against mkl in the install
> docs?
>
> For example in OSX you can use MKL by downloading
> https://github.com/intel/mkl-dnn/releases and adding MKL_RT_LIBRARY and
> MKL_INCLUDE_DIR plus -DUSE_MKL_IF_AVAILABLE=ON -DUSE_MKLML_MKL=ON
> -DUSE_MKLDNN=ON
>
> This is not documented in the website.
>
> What's the performance increase of using MKL in osx when running in CPU
> mode?
>
> Pedro
>
> On Wed, Mar 14, 2018 at 1:54 PM, Zhao, Patric <pa...@intel.com>
> wrote:
>
> > My fault, typo for your name, Larroy :(
> >
> > > -----Original Message-----
> > > From: Zhao, Patric [mailto:patric.zhao@intel.com]
> > > Sent: Wednesday, March 14, 2018 8:40 PM
> > > To: dev@mxnet.incubator.apache.org; Huang, Jin1 <ji...@intel.com>
> > > Subject: RE: call for contributions to next MXNet release
> > >
> > > Thanks, Larryo.
> > >
> > > This is a PR to fix this issue, https://github.com/apache/incubator-
> > > mxnet/pull/10075
> > > The issue will be gone after this PR is merged.
> > >
> > > For the whole logic, we are investigating now and maybe propose a new
> > > approach for Makefile and CMake.
> > >
> > > > -----Original Message-----
> > > > From: Pedro Larroy [mailto:pedro.larroy.lists@gmail.com]
> > > > Sent: Wednesday, March 14, 2018 8:31 PM
> > > > To: dev@mxnet.incubator.apache.org
> > > > Subject: Re: call for contributions to next MXNet release
> > > >
> > > > Hi
> > > >
> > > > Can you please fix the build logic?
> > > > https://github.com/apache/incubator-
> > > > mxnet/blob/master/CMakeLists.txt#L158
> > > >
> > > > https://github.com/apache/incubator-mxnet/issues/10072
> > > >
> > > > It wrongly assumes that you have MKL installed, MKLDNN needs to check
> > > > if MKL is available before, or be disabled by default, also in non
> > intel
> > > platforms.
> > > >
> > > > Pedro
> > > >
> > > > On Sun, Mar 11, 2018 at 2:43 PM, Zhao, Patric <patric.zhao@intel.com
> >
> > > > wrote:
> > > >
> > > > > Steffen, really thanks for the helps and I totally agree with you
> > > > > and Marco's suggestions.
> > > > > I will summarize the open issues and status for the review soon.
> > > > >
> > > > > > What is your github handle?
> > > > > Github ID: Patric Zhao, https://github.com/pengzhao-intel/ Da
> > Zheng,
> > > > > https://github.com/zheng-da/
> > > > >
> > > > > > - do you have design docs we can link to? Does the doc cover
> > > > > > packaging,
> > > > > use
> > > > > > of MXNet with full MKL (I understand there are license issues,
> but
> > > > > > we do
> > > > > have
> > > > > > users who are or plan to use MXNet with the complete MKL package,
> > > > > > not
> > > > > just
> > > > > > DNN subset)?
> > > > > Design doc: https://cwiki.apache.org/
> confluence/display/MXNET/The+
> > > > > design+of+MKLDNN+integration
> > > > > It's a good suggestion for the full MKL package and we will add the
> > > > > related part in the doc.
> > > > >
> > > > > > - do you have performance measurements (or plan to measure) to
> > > > > > include in release notes?
> > > > > Yes, we have tested the performance on all C4/C5 instances
> > > > > (8x,4x,2x,xlarge,large). And the accuracy are verified as well.
> > > > > We plan to publish these data both in the release note and mxnet
> > > > > website ( https://mxnet.incubator.apache.org/faq/perf.html).
> > > > >
> > > > > > - should we talk about the package at the Apr 24th meetup in
> > Seattle?
> > > > > We're based in Shanghai, China; so maybe @Da Zheng?
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > > > Sent: Sunday, March 11, 2018 6:11 PM
> > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > Cc: marco.g.abreu@googlemail.com
> > > > > > Subject: Re: call for contributions to next MXNet release
> > > > > >
> > > > > > Patric - added MKL-DNN to the project list. What is your github
> > handle?
> > > > > > I do agree with Marco that we need to resolve disable tests,
> > > > > > broken
> > > > > features
> > > > > > etc. Jira looks like the right answer to create a list of known
> > issues.
> > > > > > Questions I do have:
> > > > > > - do you have design docs we can link to? Does the doc cover
> > > > > > packaging,
> > > > > use
> > > > > > of MXNet with full MKL (I understand there are license issues,
> but
> > > > > > we do
> > > > > have
> > > > > > users who are or plan to use MXNet with the complete MKL package,
> > > > > > not
> > > > > just
> > > > > > DNN subset)?
> > > > > > - do you have performance measurements (or plan to measure) to
> > > > > > include in release notes?
> > > > > > - should we talk about the package at the Apr 24th meetup in
> > Seattle?
> > > > > >
> > > > > > Steffen
> > > > > >
> > > > > > On Sat, Mar 10, 2018 at 4:40 AM Zhao, Patric
> > > > > > <pa...@intel.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Marco,
> > > > > > >
> > > > > > > Thanks for the inputs.
> > > > > > >
> > > > > > > MKL-DNN is just merged to the master branch in a month. I agree
> > > > > > > that it's not very mature.
> > > > > > > But, in my mind, there're NO major issues in the current
> > > > > implementation.
> > > > > > >
> > > > > > > The previous data race (flaky test) issue is fixed by Zheng Da.
> > > > > > > We have submitted the PRs to fix the building issues and setup
> > > > > > > Clang CI environment, such as in OSX and Cmake.
> > > > > > > Meanwhile, we are actively working on the MXNET for the
> > > > > > > performance, functionality and usability improvements.
> > > > > > >
> > > > > > > More positively, I think we should summarize the open issues,
> > > > > > > and we can focus on these issues you've mentioned.
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > --Patric
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Marco de Abreu [mailto:marco.g.abreu@googlemail.com]
> > > > > > > > Sent: Saturday, March 10, 2018 9:36 AM
> > > > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > > > Subject: Re: call for contributions to next MXNet release
> > > > > > > >
> > > > > > > > Hello Patric,
> > > > > > > >
> > > > > > > > please be aware of the fact that there are still a lot of
> > > > > > > > disabled
> > > > > > > tests, open
> > > > > > > > MKLDNN issues, broken features and flaky tests that have not
> > > > > > > > been addressed yet. We agreed on merging MKLDNN for the time
> > > > > > > > being to allow broad testing and that we will revisit the
> > > > > > > > state a bit before the next
> > > > > > > release.
> > > > > > > > At the moment, I'd not be in favour of having MKLDNN being
> > > > > > > > part of
> > > > > it.
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Marco
> > > > > > > >
> > > > > > > > Zhao, Patric <pa...@intel.com> schrieb am Sa., 10.
> März
> > > > > > > > 2018,
> > > > > > > 02:30:
> > > > > > > >
> > > > > > > > > Hi Steffen,
> > > > > > > > >
> > > > > > > > > We'd like the MKL-DNN backend can be included in the next
> > > release.
> > > > > > > > >
> > > > > > > > > We (Intel engineers) and Zheng-Da (AWS engineer) can work
> > on it.
> > > > > > > > >
> > > > > > > > > Could you help add the item in the table?
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > >
> > > > > > > > > --Patric
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > > > > > > > Sent: Friday, March 9, 2018 9:29 PM
> > > > > > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > > > > > Subject: call for contributions to next MXNet release
> > > > > > > > > >
> > > > > > > > > > Hi - I would like to propose the next MXNet release.
> > > > > > > > > > Initial draft content is listed at MXNet wiki
> > > > > > > > > > <https://cwiki.apache.org/confluence/display/MXNET/
> Project
> > > > > > > > > > +P
> > > > > > > > > > ropo
> > > > > > > > > > sals
> > > > > > > > > > +fo
> > > > > > > > > > r+next+MXNet+Release>.
> > > > > > > > > > I would like to call to all contributors to add features
> > > > > > > > > > you are working
> > > > > > > > > on and
> > > > > > > > > > would like to see included in the release. Suggested code
> > > > > > > > > > freeze is March 30th with target release by mid April.
> > > > > > > > > >
> > > > > > > > > > Anirudh Subramanian and Chris Olivier have volunteered to
> > > > > > > > > > co-manage the release.
> > > > > > > > > >
> > > > > > > > > > Mark your date: we are planing public meetup on Apr 24th
> > > > > > > > > > in
> > > > > Seattle.
> > > > > > > > > > Details to follow.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Steffen
> > > > > > > > >
> > > > > > >
> > > > >
> >
>
Re: call for contributions to next MXNet release
Posted by Pedro Larroy <pe...@gmail.com>.
Hi Patric
Does it make sense to add instructions to link against mkl in the install
docs?
For example in OSX you can use MKL by downloading
https://github.com/intel/mkl-dnn/releases and adding MKL_RT_LIBRARY and
MKL_INCLUDE_DIR plus -DUSE_MKL_IF_AVAILABLE=ON -DUSE_MKLML_MKL=ON
-DUSE_MKLDNN=ON
This is not documented in the website.
What's the performance increase of using MKL in osx when running in CPU
mode?
Pedro
On Wed, Mar 14, 2018 at 1:54 PM, Zhao, Patric <pa...@intel.com> wrote:
> My fault, typo for your name, Larroy :(
>
> > -----Original Message-----
> > From: Zhao, Patric [mailto:patric.zhao@intel.com]
> > Sent: Wednesday, March 14, 2018 8:40 PM
> > To: dev@mxnet.incubator.apache.org; Huang, Jin1 <ji...@intel.com>
> > Subject: RE: call for contributions to next MXNet release
> >
> > Thanks, Larryo.
> >
> > This is a PR to fix this issue, https://github.com/apache/incubator-
> > mxnet/pull/10075
> > The issue will be gone after this PR is merged.
> >
> > For the whole logic, we are investigating now and maybe propose a new
> > approach for Makefile and CMake.
> >
> > > -----Original Message-----
> > > From: Pedro Larroy [mailto:pedro.larroy.lists@gmail.com]
> > > Sent: Wednesday, March 14, 2018 8:31 PM
> > > To: dev@mxnet.incubator.apache.org
> > > Subject: Re: call for contributions to next MXNet release
> > >
> > > Hi
> > >
> > > Can you please fix the build logic?
> > > https://github.com/apache/incubator-
> > > mxnet/blob/master/CMakeLists.txt#L158
> > >
> > > https://github.com/apache/incubator-mxnet/issues/10072
> > >
> > > It wrongly assumes that you have MKL installed, MKLDNN needs to check
> > > if MKL is available before, or be disabled by default, also in non
> intel
> > platforms.
> > >
> > > Pedro
> > >
> > > On Sun, Mar 11, 2018 at 2:43 PM, Zhao, Patric <pa...@intel.com>
> > > wrote:
> > >
> > > > Steffen, really thanks for the helps and I totally agree with you
> > > > and Marco's suggestions.
> > > > I will summarize the open issues and status for the review soon.
> > > >
> > > > > What is your github handle?
> > > > Github ID: Patric Zhao, https://github.com/pengzhao-intel/ Da
> Zheng,
> > > > https://github.com/zheng-da/
> > > >
> > > > > - do you have design docs we can link to? Does the doc cover
> > > > > packaging,
> > > > use
> > > > > of MXNet with full MKL (I understand there are license issues, but
> > > > > we do
> > > > have
> > > > > users who are or plan to use MXNet with the complete MKL package,
> > > > > not
> > > > just
> > > > > DNN subset)?
> > > > Design doc: https://cwiki.apache.org/confluence/display/MXNET/The+
> > > > design+of+MKLDNN+integration
> > > > It's a good suggestion for the full MKL package and we will add the
> > > > related part in the doc.
> > > >
> > > > > - do you have performance measurements (or plan to measure) to
> > > > > include in release notes?
> > > > Yes, we have tested the performance on all C4/C5 instances
> > > > (8x,4x,2x,xlarge,large). And the accuracy are verified as well.
> > > > We plan to publish these data both in the release note and mxnet
> > > > website ( https://mxnet.incubator.apache.org/faq/perf.html).
> > > >
> > > > > - should we talk about the package at the Apr 24th meetup in
> Seattle?
> > > > We're based in Shanghai, China; so maybe @Da Zheng?
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > > Sent: Sunday, March 11, 2018 6:11 PM
> > > > > To: dev@mxnet.incubator.apache.org
> > > > > Cc: marco.g.abreu@googlemail.com
> > > > > Subject: Re: call for contributions to next MXNet release
> > > > >
> > > > > Patric - added MKL-DNN to the project list. What is your github
> handle?
> > > > > I do agree with Marco that we need to resolve disable tests,
> > > > > broken
> > > > features
> > > > > etc. Jira looks like the right answer to create a list of known
> issues.
> > > > > Questions I do have:
> > > > > - do you have design docs we can link to? Does the doc cover
> > > > > packaging,
> > > > use
> > > > > of MXNet with full MKL (I understand there are license issues, but
> > > > > we do
> > > > have
> > > > > users who are or plan to use MXNet with the complete MKL package,
> > > > > not
> > > > just
> > > > > DNN subset)?
> > > > > - do you have performance measurements (or plan to measure) to
> > > > > include in release notes?
> > > > > - should we talk about the package at the Apr 24th meetup in
> Seattle?
> > > > >
> > > > > Steffen
> > > > >
> > > > > On Sat, Mar 10, 2018 at 4:40 AM Zhao, Patric
> > > > > <pa...@intel.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Marco,
> > > > > >
> > > > > > Thanks for the inputs.
> > > > > >
> > > > > > MKL-DNN is just merged to the master branch in a month. I agree
> > > > > > that it's not very mature.
> > > > > > But, in my mind, there're NO major issues in the current
> > > > implementation.
> > > > > >
> > > > > > The previous data race (flaky test) issue is fixed by Zheng Da.
> > > > > > We have submitted the PRs to fix the building issues and setup
> > > > > > Clang CI environment, such as in OSX and Cmake.
> > > > > > Meanwhile, we are actively working on the MXNET for the
> > > > > > performance, functionality and usability improvements.
> > > > > >
> > > > > > More positively, I think we should summarize the open issues,
> > > > > > and we can focus on these issues you've mentioned.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > --Patric
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Marco de Abreu [mailto:marco.g.abreu@googlemail.com]
> > > > > > > Sent: Saturday, March 10, 2018 9:36 AM
> > > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > > Subject: Re: call for contributions to next MXNet release
> > > > > > >
> > > > > > > Hello Patric,
> > > > > > >
> > > > > > > please be aware of the fact that there are still a lot of
> > > > > > > disabled
> > > > > > tests, open
> > > > > > > MKLDNN issues, broken features and flaky tests that have not
> > > > > > > been addressed yet. We agreed on merging MKLDNN for the time
> > > > > > > being to allow broad testing and that we will revisit the
> > > > > > > state a bit before the next
> > > > > > release.
> > > > > > > At the moment, I'd not be in favour of having MKLDNN being
> > > > > > > part of
> > > > it.
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Marco
> > > > > > >
> > > > > > > Zhao, Patric <pa...@intel.com> schrieb am Sa., 10. März
> > > > > > > 2018,
> > > > > > 02:30:
> > > > > > >
> > > > > > > > Hi Steffen,
> > > > > > > >
> > > > > > > > We'd like the MKL-DNN backend can be included in the next
> > release.
> > > > > > > >
> > > > > > > > We (Intel engineers) and Zheng-Da (AWS engineer) can work
> on it.
> > > > > > > >
> > > > > > > > Could you help add the item in the table?
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > >
> > > > > > > > --Patric
> > > > > > > >
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > > > > > > Sent: Friday, March 9, 2018 9:29 PM
> > > > > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > > > > Subject: call for contributions to next MXNet release
> > > > > > > > >
> > > > > > > > > Hi - I would like to propose the next MXNet release.
> > > > > > > > > Initial draft content is listed at MXNet wiki
> > > > > > > > > <https://cwiki.apache.org/confluence/display/MXNET/Project
> > > > > > > > > +P
> > > > > > > > > ropo
> > > > > > > > > sals
> > > > > > > > > +fo
> > > > > > > > > r+next+MXNet+Release>.
> > > > > > > > > I would like to call to all contributors to add features
> > > > > > > > > you are working
> > > > > > > > on and
> > > > > > > > > would like to see included in the release. Suggested code
> > > > > > > > > freeze is March 30th with target release by mid April.
> > > > > > > > >
> > > > > > > > > Anirudh Subramanian and Chris Olivier have volunteered to
> > > > > > > > > co-manage the release.
> > > > > > > > >
> > > > > > > > > Mark your date: we are planing public meetup on Apr 24th
> > > > > > > > > in
> > > > Seattle.
> > > > > > > > > Details to follow.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Steffen
> > > > > > > >
> > > > > >
> > > >
>
RE: call for contributions to next MXNet release
Posted by "Zhao, Patric" <pa...@intel.com>.
My fault, typo for your name, Larroy :(
> -----Original Message-----
> From: Zhao, Patric [mailto:patric.zhao@intel.com]
> Sent: Wednesday, March 14, 2018 8:40 PM
> To: dev@mxnet.incubator.apache.org; Huang, Jin1 <ji...@intel.com>
> Subject: RE: call for contributions to next MXNet release
>
> Thanks, Larryo.
>
> This is a PR to fix this issue, https://github.com/apache/incubator-
> mxnet/pull/10075
> The issue will be gone after this PR is merged.
>
> For the whole logic, we are investigating now and maybe propose a new
> approach for Makefile and CMake.
>
> > -----Original Message-----
> > From: Pedro Larroy [mailto:pedro.larroy.lists@gmail.com]
> > Sent: Wednesday, March 14, 2018 8:31 PM
> > To: dev@mxnet.incubator.apache.org
> > Subject: Re: call for contributions to next MXNet release
> >
> > Hi
> >
> > Can you please fix the build logic?
> > https://github.com/apache/incubator-
> > mxnet/blob/master/CMakeLists.txt#L158
> >
> > https://github.com/apache/incubator-mxnet/issues/10072
> >
> > It wrongly assumes that you have MKL installed, MKLDNN needs to check
> > if MKL is available before, or be disabled by default, also in non intel
> platforms.
> >
> > Pedro
> >
> > On Sun, Mar 11, 2018 at 2:43 PM, Zhao, Patric <pa...@intel.com>
> > wrote:
> >
> > > Steffen, really thanks for the helps and I totally agree with you
> > > and Marco's suggestions.
> > > I will summarize the open issues and status for the review soon.
> > >
> > > > What is your github handle?
> > > Github ID: Patric Zhao, https://github.com/pengzhao-intel/ Da Zheng,
> > > https://github.com/zheng-da/
> > >
> > > > - do you have design docs we can link to? Does the doc cover
> > > > packaging,
> > > use
> > > > of MXNet with full MKL (I understand there are license issues, but
> > > > we do
> > > have
> > > > users who are or plan to use MXNet with the complete MKL package,
> > > > not
> > > just
> > > > DNN subset)?
> > > Design doc: https://cwiki.apache.org/confluence/display/MXNET/The+
> > > design+of+MKLDNN+integration
> > > It's a good suggestion for the full MKL package and we will add the
> > > related part in the doc.
> > >
> > > > - do you have performance measurements (or plan to measure) to
> > > > include in release notes?
> > > Yes, we have tested the performance on all C4/C5 instances
> > > (8x,4x,2x,xlarge,large). And the accuracy are verified as well.
> > > We plan to publish these data both in the release note and mxnet
> > > website ( https://mxnet.incubator.apache.org/faq/perf.html).
> > >
> > > > - should we talk about the package at the Apr 24th meetup in Seattle?
> > > We're based in Shanghai, China; so maybe @Da Zheng?
> > >
> > >
> > > > -----Original Message-----
> > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > Sent: Sunday, March 11, 2018 6:11 PM
> > > > To: dev@mxnet.incubator.apache.org
> > > > Cc: marco.g.abreu@googlemail.com
> > > > Subject: Re: call for contributions to next MXNet release
> > > >
> > > > Patric - added MKL-DNN to the project list. What is your github handle?
> > > > I do agree with Marco that we need to resolve disable tests,
> > > > broken
> > > features
> > > > etc. Jira looks like the right answer to create a list of known issues.
> > > > Questions I do have:
> > > > - do you have design docs we can link to? Does the doc cover
> > > > packaging,
> > > use
> > > > of MXNet with full MKL (I understand there are license issues, but
> > > > we do
> > > have
> > > > users who are or plan to use MXNet with the complete MKL package,
> > > > not
> > > just
> > > > DNN subset)?
> > > > - do you have performance measurements (or plan to measure) to
> > > > include in release notes?
> > > > - should we talk about the package at the Apr 24th meetup in Seattle?
> > > >
> > > > Steffen
> > > >
> > > > On Sat, Mar 10, 2018 at 4:40 AM Zhao, Patric
> > > > <pa...@intel.com>
> > > > wrote:
> > > >
> > > > > Hi Marco,
> > > > >
> > > > > Thanks for the inputs.
> > > > >
> > > > > MKL-DNN is just merged to the master branch in a month. I agree
> > > > > that it's not very mature.
> > > > > But, in my mind, there're NO major issues in the current
> > > implementation.
> > > > >
> > > > > The previous data race (flaky test) issue is fixed by Zheng Da.
> > > > > We have submitted the PRs to fix the building issues and setup
> > > > > Clang CI environment, such as in OSX and Cmake.
> > > > > Meanwhile, we are actively working on the MXNET for the
> > > > > performance, functionality and usability improvements.
> > > > >
> > > > > More positively, I think we should summarize the open issues,
> > > > > and we can focus on these issues you've mentioned.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > --Patric
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Marco de Abreu [mailto:marco.g.abreu@googlemail.com]
> > > > > > Sent: Saturday, March 10, 2018 9:36 AM
> > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > Subject: Re: call for contributions to next MXNet release
> > > > > >
> > > > > > Hello Patric,
> > > > > >
> > > > > > please be aware of the fact that there are still a lot of
> > > > > > disabled
> > > > > tests, open
> > > > > > MKLDNN issues, broken features and flaky tests that have not
> > > > > > been addressed yet. We agreed on merging MKLDNN for the time
> > > > > > being to allow broad testing and that we will revisit the
> > > > > > state a bit before the next
> > > > > release.
> > > > > > At the moment, I'd not be in favour of having MKLDNN being
> > > > > > part of
> > > it.
> > > > > >
> > > > > > Best regards,
> > > > > > Marco
> > > > > >
> > > > > > Zhao, Patric <pa...@intel.com> schrieb am Sa., 10. März
> > > > > > 2018,
> > > > > 02:30:
> > > > > >
> > > > > > > Hi Steffen,
> > > > > > >
> > > > > > > We'd like the MKL-DNN backend can be included in the next
> release.
> > > > > > >
> > > > > > > We (Intel engineers) and Zheng-Da (AWS engineer) can work on it.
> > > > > > >
> > > > > > > Could you help add the item in the table?
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > --Patric
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > > > > > Sent: Friday, March 9, 2018 9:29 PM
> > > > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > > > Subject: call for contributions to next MXNet release
> > > > > > > >
> > > > > > > > Hi - I would like to propose the next MXNet release.
> > > > > > > > Initial draft content is listed at MXNet wiki
> > > > > > > > <https://cwiki.apache.org/confluence/display/MXNET/Project
> > > > > > > > +P
> > > > > > > > ropo
> > > > > > > > sals
> > > > > > > > +fo
> > > > > > > > r+next+MXNet+Release>.
> > > > > > > > I would like to call to all contributors to add features
> > > > > > > > you are working
> > > > > > > on and
> > > > > > > > would like to see included in the release. Suggested code
> > > > > > > > freeze is March 30th with target release by mid April.
> > > > > > > >
> > > > > > > > Anirudh Subramanian and Chris Olivier have volunteered to
> > > > > > > > co-manage the release.
> > > > > > > >
> > > > > > > > Mark your date: we are planing public meetup on Apr 24th
> > > > > > > > in
> > > Seattle.
> > > > > > > > Details to follow.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Steffen
> > > > > > >
> > > > >
> > >
RE: call for contributions to next MXNet release
Posted by "Zhao, Patric" <pa...@intel.com>.
Thanks, Larryo.
This is a PR to fix this issue, https://github.com/apache/incubator-mxnet/pull/10075
The issue will be gone after this PR is merged.
For the whole logic, we are investigating now and maybe propose a new approach for Makefile and CMake.
> -----Original Message-----
> From: Pedro Larroy [mailto:pedro.larroy.lists@gmail.com]
> Sent: Wednesday, March 14, 2018 8:31 PM
> To: dev@mxnet.incubator.apache.org
> Subject: Re: call for contributions to next MXNet release
>
> Hi
>
> Can you please fix the build logic?
> https://github.com/apache/incubator-
> mxnet/blob/master/CMakeLists.txt#L158
>
> https://github.com/apache/incubator-mxnet/issues/10072
>
> It wrongly assumes that you have MKL installed, MKLDNN needs to check if
> MKL is available before, or be disabled by default, also in non intel platforms.
>
> Pedro
>
> On Sun, Mar 11, 2018 at 2:43 PM, Zhao, Patric <pa...@intel.com>
> wrote:
>
> > Steffen, really thanks for the helps and I totally agree with you and
> > Marco's suggestions.
> > I will summarize the open issues and status for the review soon.
> >
> > > What is your github handle?
> > Github ID: Patric Zhao, https://github.com/pengzhao-intel/ Da Zheng,
> > https://github.com/zheng-da/
> >
> > > - do you have design docs we can link to? Does the doc cover
> > > packaging,
> > use
> > > of MXNet with full MKL (I understand there are license issues, but
> > > we do
> > have
> > > users who are or plan to use MXNet with the complete MKL package,
> > > not
> > just
> > > DNN subset)?
> > Design doc: https://cwiki.apache.org/confluence/display/MXNET/The+
> > design+of+MKLDNN+integration
> > It's a good suggestion for the full MKL package and we will add the
> > related part in the doc.
> >
> > > - do you have performance measurements (or plan to measure) to
> > > include in release notes?
> > Yes, we have tested the performance on all C4/C5 instances
> > (8x,4x,2x,xlarge,large). And the accuracy are verified as well.
> > We plan to publish these data both in the release note and mxnet
> > website ( https://mxnet.incubator.apache.org/faq/perf.html).
> >
> > > - should we talk about the package at the Apr 24th meetup in Seattle?
> > We're based in Shanghai, China; so maybe @Da Zheng?
> >
> >
> > > -----Original Message-----
> > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > Sent: Sunday, March 11, 2018 6:11 PM
> > > To: dev@mxnet.incubator.apache.org
> > > Cc: marco.g.abreu@googlemail.com
> > > Subject: Re: call for contributions to next MXNet release
> > >
> > > Patric - added MKL-DNN to the project list. What is your github handle?
> > > I do agree with Marco that we need to resolve disable tests, broken
> > features
> > > etc. Jira looks like the right answer to create a list of known issues.
> > > Questions I do have:
> > > - do you have design docs we can link to? Does the doc cover
> > > packaging,
> > use
> > > of MXNet with full MKL (I understand there are license issues, but
> > > we do
> > have
> > > users who are or plan to use MXNet with the complete MKL package,
> > > not
> > just
> > > DNN subset)?
> > > - do you have performance measurements (or plan to measure) to
> > > include in release notes?
> > > - should we talk about the package at the Apr 24th meetup in Seattle?
> > >
> > > Steffen
> > >
> > > On Sat, Mar 10, 2018 at 4:40 AM Zhao, Patric <pa...@intel.com>
> > > wrote:
> > >
> > > > Hi Marco,
> > > >
> > > > Thanks for the inputs.
> > > >
> > > > MKL-DNN is just merged to the master branch in a month. I agree
> > > > that it's not very mature.
> > > > But, in my mind, there're NO major issues in the current
> > implementation.
> > > >
> > > > The previous data race (flaky test) issue is fixed by Zheng Da.
> > > > We have submitted the PRs to fix the building issues and setup
> > > > Clang CI environment, such as in OSX and Cmake.
> > > > Meanwhile, we are actively working on the MXNET for the
> > > > performance, functionality and usability improvements.
> > > >
> > > > More positively, I think we should summarize the open issues, and
> > > > we can focus on these issues you've mentioned.
> > > >
> > > > Thanks,
> > > >
> > > > --Patric
> > > >
> > > > > -----Original Message-----
> > > > > From: Marco de Abreu [mailto:marco.g.abreu@googlemail.com]
> > > > > Sent: Saturday, March 10, 2018 9:36 AM
> > > > > To: dev@mxnet.incubator.apache.org
> > > > > Subject: Re: call for contributions to next MXNet release
> > > > >
> > > > > Hello Patric,
> > > > >
> > > > > please be aware of the fact that there are still a lot of
> > > > > disabled
> > > > tests, open
> > > > > MKLDNN issues, broken features and flaky tests that have not
> > > > > been addressed yet. We agreed on merging MKLDNN for the time
> > > > > being to allow broad testing and that we will revisit the state
> > > > > a bit before the next
> > > > release.
> > > > > At the moment, I'd not be in favour of having MKLDNN being part
> > > > > of
> > it.
> > > > >
> > > > > Best regards,
> > > > > Marco
> > > > >
> > > > > Zhao, Patric <pa...@intel.com> schrieb am Sa., 10. März
> > > > > 2018,
> > > > 02:30:
> > > > >
> > > > > > Hi Steffen,
> > > > > >
> > > > > > We'd like the MKL-DNN backend can be included in the next release.
> > > > > >
> > > > > > We (Intel engineers) and Zheng-Da (AWS engineer) can work on it.
> > > > > >
> > > > > > Could you help add the item in the table?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > --Patric
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > > > > Sent: Friday, March 9, 2018 9:29 PM
> > > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > > Subject: call for contributions to next MXNet release
> > > > > > >
> > > > > > > Hi - I would like to propose the next MXNet release.
> > > > > > > Initial draft content is listed at MXNet wiki
> > > > > > > <https://cwiki.apache.org/confluence/display/MXNET/Project+P
> > > > > > > ropo
> > > > > > > sals
> > > > > > > +fo
> > > > > > > r+next+MXNet+Release>.
> > > > > > > I would like to call to all contributors to add features you
> > > > > > > are working
> > > > > > on and
> > > > > > > would like to see included in the release. Suggested code
> > > > > > > freeze is March 30th with target release by mid April.
> > > > > > >
> > > > > > > Anirudh Subramanian and Chris Olivier have volunteered to
> > > > > > > co-manage the release.
> > > > > > >
> > > > > > > Mark your date: we are planing public meetup on Apr 24th in
> > Seattle.
> > > > > > > Details to follow.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Steffen
> > > > > >
> > > >
> >
Re: call for contributions to next MXNet release
Posted by Pedro Larroy <pe...@gmail.com>.
Hi
Can you please fix the build logic?
https://github.com/apache/incubator-mxnet/blob/master/CMakeLists.txt#L158
https://github.com/apache/incubator-mxnet/issues/10072
It wrongly assumes that you have MKL installed, MKLDNN needs to check if
MKL is available before, or be disabled by default, also in non intel
platforms.
Pedro
On Sun, Mar 11, 2018 at 2:43 PM, Zhao, Patric <pa...@intel.com> wrote:
> Steffen, really thanks for the helps and I totally agree with you and
> Marco's suggestions.
> I will summarize the open issues and status for the review soon.
>
> > What is your github handle?
> Github ID: Patric Zhao, https://github.com/pengzhao-intel/ Da Zheng,
> https://github.com/zheng-da/
>
> > - do you have design docs we can link to? Does the doc cover packaging,
> use
> > of MXNet with full MKL (I understand there are license issues, but we do
> have
> > users who are or plan to use MXNet with the complete MKL package, not
> just
> > DNN subset)?
> Design doc: https://cwiki.apache.org/confluence/display/MXNET/The+
> design+of+MKLDNN+integration
> It's a good suggestion for the full MKL package and we will add the
> related part in the doc.
>
> > - do you have performance measurements (or plan to measure) to include in
> > release notes?
> Yes, we have tested the performance on all C4/C5 instances
> (8x,4x,2x,xlarge,large). And the accuracy are verified as well.
> We plan to publish these data both in the release note and mxnet website (
> https://mxnet.incubator.apache.org/faq/perf.html).
>
> > - should we talk about the package at the Apr 24th meetup in Seattle?
> We're based in Shanghai, China; so maybe @Da Zheng?
>
>
> > -----Original Message-----
> > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > Sent: Sunday, March 11, 2018 6:11 PM
> > To: dev@mxnet.incubator.apache.org
> > Cc: marco.g.abreu@googlemail.com
> > Subject: Re: call for contributions to next MXNet release
> >
> > Patric - added MKL-DNN to the project list. What is your github handle?
> > I do agree with Marco that we need to resolve disable tests, broken
> features
> > etc. Jira looks like the right answer to create a list of known issues.
> > Questions I do have:
> > - do you have design docs we can link to? Does the doc cover packaging,
> use
> > of MXNet with full MKL (I understand there are license issues, but we do
> have
> > users who are or plan to use MXNet with the complete MKL package, not
> just
> > DNN subset)?
> > - do you have performance measurements (or plan to measure) to include in
> > release notes?
> > - should we talk about the package at the Apr 24th meetup in Seattle?
> >
> > Steffen
> >
> > On Sat, Mar 10, 2018 at 4:40 AM Zhao, Patric <pa...@intel.com>
> > wrote:
> >
> > > Hi Marco,
> > >
> > > Thanks for the inputs.
> > >
> > > MKL-DNN is just merged to the master branch in a month. I agree that
> > > it's not very mature.
> > > But, in my mind, there're NO major issues in the current
> implementation.
> > >
> > > The previous data race (flaky test) issue is fixed by Zheng Da.
> > > We have submitted the PRs to fix the building issues and setup Clang
> > > CI environment, such as in OSX and Cmake.
> > > Meanwhile, we are actively working on the MXNET for the performance,
> > > functionality and usability improvements.
> > >
> > > More positively, I think we should summarize the open issues, and we
> > > can focus on these issues you've mentioned.
> > >
> > > Thanks,
> > >
> > > --Patric
> > >
> > > > -----Original Message-----
> > > > From: Marco de Abreu [mailto:marco.g.abreu@googlemail.com]
> > > > Sent: Saturday, March 10, 2018 9:36 AM
> > > > To: dev@mxnet.incubator.apache.org
> > > > Subject: Re: call for contributions to next MXNet release
> > > >
> > > > Hello Patric,
> > > >
> > > > please be aware of the fact that there are still a lot of disabled
> > > tests, open
> > > > MKLDNN issues, broken features and flaky tests that have not been
> > > > addressed yet. We agreed on merging MKLDNN for the time being to
> > > > allow broad testing and that we will revisit the state a bit before
> > > > the next
> > > release.
> > > > At the moment, I'd not be in favour of having MKLDNN being part of
> it.
> > > >
> > > > Best regards,
> > > > Marco
> > > >
> > > > Zhao, Patric <pa...@intel.com> schrieb am Sa., 10. März 2018,
> > > 02:30:
> > > >
> > > > > Hi Steffen,
> > > > >
> > > > > We'd like the MKL-DNN backend can be included in the next release.
> > > > >
> > > > > We (Intel engineers) and Zheng-Da (AWS engineer) can work on it.
> > > > >
> > > > > Could you help add the item in the table?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > --Patric
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > > > Sent: Friday, March 9, 2018 9:29 PM
> > > > > > To: dev@mxnet.incubator.apache.org
> > > > > > Subject: call for contributions to next MXNet release
> > > > > >
> > > > > > Hi - I would like to propose the next MXNet release.
> > > > > > Initial draft content is listed at MXNet wiki
> > > > > > <https://cwiki.apache.org/confluence/display/MXNET/Project+Propo
> > > > > > sals
> > > > > > +fo
> > > > > > r+next+MXNet+Release>.
> > > > > > I would like to call to all contributors to add features you are
> > > > > > working
> > > > > on and
> > > > > > would like to see included in the release. Suggested code freeze
> > > > > > is March 30th with target release by mid April.
> > > > > >
> > > > > > Anirudh Subramanian and Chris Olivier have volunteered to
> > > > > > co-manage the release.
> > > > > >
> > > > > > Mark your date: we are planing public meetup on Apr 24th in
> Seattle.
> > > > > > Details to follow.
> > > > > >
> > > > > > Regards,
> > > > > > Steffen
> > > > >
> > >
>
RE: call for contributions to next MXNet release
Posted by "Zhao, Patric" <pa...@intel.com>.
Really thank Marco, Da and other reviewers' help :)
I'd like to update the status of MKL-DNN bugs.
Feel free to let me know if there're any other issues.
There're 8 opened issues (1 discussion thread is not included).
2 issues are WIP and will be completed in next several days.
#10189, Race condition when MKLDNN is enabled MKL, Zheng Da
Note: this data race exist in theory but couldn't happen now. Da is working on the enhancement to make it perfect.
-#8712, test_operator.test_depthwise_convolution fails in [Python2: MKLML-CPU] and [Python3: MKLML-CPU], Patric Zhao
6 opened issues have been resolved and wait to review/merge/close
#10168 (PR#10218) CPP test case fails to compile using gcc 4.8.5 when MKLDNN enabled Breaking Build MKL
#10141 (Passed, to be closed) Flaky test test_operator_gpu.test_convolution_options @ Python2: MKLDNN-GPU Flaky MKL Test
#10092 (PR#10021) No "full" pooling convention support with MKL-DNN Feature request MKL Operator
#10026 (PR#10069) MXNET_MKLDNN_DEBUG=1 produces errors Bug MKL
#8974 (Question, will update doc) MXNET compatibility with MKL libraries bundled in Microsoft R Open MKL
#8532 (resolved by workaround) mxnet-mkl (v0.12.0) crash when using (conda-installed) numpy with MKL Bug MKL
Note: The duplicated libiomp.so library caused the conflict in the conda and it's not introduced by MKL-DNN.
It can be resolved by environment variable. I am looking for C API to set in the runtime.
> -----Original Message-----
> From: Marco de Abreu [mailto:marco.g.abreu@googlemail.com]
> Sent: Saturday, March 17, 2018 1:37 AM
> To: dev@mxnet.incubator.apache.org
> Subject: Re: call for contributions to next MXNet release
>
> Hi Patric,
>
> I have added three more issues:
> https://github.com/apache/incubator-mxnet/issues/10131
> https://github.com/apache/incubator-mxnet/issues/10133
> https://github.com/apache/incubator-mxnet/issues/10134
>
> Also, you missed https://github.com/apache/incubator-mxnet/issues/8712 -
> sorry, it was not labelled before
>
> Best regards,
> Marco
>
> On Fri, Mar 16, 2018 at 7:45 AM, Zhao, Patric <pa...@intel.com>
> wrote:
>
> > MKL issues summary:
> >
> > Feel free to let me know if anything I missed.
> >
> > Totally, there’re 11 open issues in the github with the label of MKL
> > as
> > below:
> > 4 Bugs issues: #10092, #10086, #10026, #8881
> > 4 Building issues: #9993, #9828, #8974, #8532
> > 1 Flaky Tests: #9864
> > 2 wrong label and invalidated: #9844, #8874
> >
> > Current status.
> > 3 DONE, to be closed.
> > 4 WIP (working in progress)
> > 2 TODO
> > 2 are invalidated now.
> >
> > Details:
> > #10092, WIP, PR#10021
> > #10086, TODO
> > #10026, WIP
> > #9993, DONE (need to be closed), fixed by #10075 #9864, TODO #9844,
> > INVALIDED, not related w/ MKL #9828, DONE (need to be closed), fixed
> > by #9918 & #10115 #8974, WIP #8881, DONE (need to be closed), fixed by
> > #9112 #8874, INVALIDED, “I believe, we are not using MKL”
> > #8532, WIP, library conflict and can be resolved by environment
> > setting
> >
> > Lists:
> > No "full" pooling convention support with MKL-DNN Feature request MKL
> > Operator
> > #10092 opened 2 days ago by marcoabreu
> > https://github.com/apache/incubator-mxnet/issues/10092
> >
> > [MXNET-84] Segfault test_autograd.test_unary_func @ Python3:
> > MKLDNN-CPU Bug MKL Test
> > #10086 opened 3 days ago by marcoabreu
> > https://github.com/apache/incubator-mxnet/issues/10086
> >
> > MXNET_MKLDNN_DEBUG=1 produces errors Bug MKL
> > #10026 opened 8 days ago by marcoabreu
> > https://github.com/apache/incubator-mxnet/issues/10026
> >
> > cmake cannot build mxnet Bug Build MKL
> > #9993 opened 11 days ago by jacky4323
> > https://github.com/apache/incubator-mxnet/issues/9993
> >
> > Flaky hanging test_operator.test_laop_3 @ Python3: MKLDNN-CPU Flaky
> > MKL Test
> > #9864 opened 21 days ago by marcoabreu
> > https://github.com/apache/incubator-mxnet/issues/9864
> >
> > Flaky test_operator_gpu.test_binary_op @ Python3: MKLDNN-GPU Flaky
> MKL
> > Test
> > #9844 opened 23 days ago by marcoabreu
> > https://github.com/apache/incubator-mxnet/issues/9844
> >
> > Building with MKL fails on OSX Build MKL
> > #9828 opened 25 days ago by sbodenstein
> > https://github.com/apache/incubator-mxnet/issues/9828
> >
> > MXNET compatibility with MKL libraries bundled in Microsoft R Open MKL
> > #8974 opened on Dec 7, 2017 by mjmg
> > https://github.com/apache/incubator-mxnet/issues/8974
> >
> > Intel MKL FATAL ERROR: Cannot load libmkl_avx512_mic.so or
> libmkl_def.so.
> > Bug Data-loading MKL
> > #8881 opened on Nov 30, 2017 by wuzhijiexia
> > https://github.com/apache/incubator-mxnet/issues/8881
> >
> > mxnet installation from source: C++ linkage error on HPC C++
> > Installation MKL
> > #8874 opened on Nov 30, 2017 by jerrin92
> > https://github.com/apache/incubator-mxnet/issues/8874
> >
> > mxnet-mkl (v0.12.0) crash when using (conda-installed) numpy with MKL
> > Bug MKL
> > #8532 opened on Nov 3, 2017 by fhieber
> > https://github.com/apache/incubator-mxnet/issues/8532
> >
> >
> > > -----Original Message-----
> > > From: Zheng, Da [mailto:dzzhen@amazon.com]
> > > Sent: Tuesday, March 13, 2018 2:06 AM
> > > To: Zhao, Patric <pa...@intel.com>; steffenrochel@gmail.com;
> > > dev@mxnet.incubator.apache.org
> > > Cc: marco.g.abreu@googlemail.com; Ye, Jason Y <ja...@intel.com>
> > > Subject: Re: call for contributions to next MXNet release
> > >
> > > Patric, thanks for summarizing open issues.
> > >
> > > Since I'm in the Palo Alto office, maybe we don't need to wait until
> > > Apr
> > 24th?
> > >
> > > Best,
> > > Da
> > >
> > > On 3/11/18, 6:43 AM, "Zhao, Patric" <pa...@intel.com> wrote:
> > >
> > > >- should we talk about the package at the Apr 24th meetup in
> > Seattle?
> > > We're based in Shanghai, China; so maybe @Da Zheng?
> >
> >
Re: call for contributions to next MXNet release
Posted by Marco de Abreu <ma...@googlemail.com>.
Hi Patric,
I have added three more issues:
https://github.com/apache/incubator-mxnet/issues/10131
https://github.com/apache/incubator-mxnet/issues/10133
https://github.com/apache/incubator-mxnet/issues/10134
Also, you missed https://github.com/apache/incubator-mxnet/issues/8712 -
sorry, it was not labelled before
Best regards,
Marco
On Fri, Mar 16, 2018 at 7:45 AM, Zhao, Patric <pa...@intel.com> wrote:
> MKL issues summary:
>
> Feel free to let me know if anything I missed.
>
> Totally, there’re 11 open issues in the github with the label of MKL as
> below:
> 4 Bugs issues: #10092, #10086, #10026, #8881
> 4 Building issues: #9993, #9828, #8974, #8532
> 1 Flaky Tests: #9864
> 2 wrong label and invalidated: #9844, #8874
>
> Current status.
> 3 DONE, to be closed.
> 4 WIP (working in progress)
> 2 TODO
> 2 are invalidated now.
>
> Details:
> #10092, WIP, PR#10021
> #10086, TODO
> #10026, WIP
> #9993, DONE (need to be closed), fixed by #10075
> #9864, TODO
> #9844, INVALIDED, not related w/ MKL
> #9828, DONE (need to be closed), fixed by #9918 & #10115
> #8974, WIP
> #8881, DONE (need to be closed), fixed by #9112
> #8874, INVALIDED, “I believe, we are not using MKL”
> #8532, WIP, library conflict and can be resolved by environment setting
>
> Lists:
> No "full" pooling convention support with MKL-DNN Feature request MKL
> Operator
> #10092 opened 2 days ago by marcoabreu
> https://github.com/apache/incubator-mxnet/issues/10092
>
> [MXNET-84] Segfault test_autograd.test_unary_func @ Python3: MKLDNN-CPU
> Bug MKL Test
> #10086 opened 3 days ago by marcoabreu
> https://github.com/apache/incubator-mxnet/issues/10086
>
> MXNET_MKLDNN_DEBUG=1 produces errors Bug MKL
> #10026 opened 8 days ago by marcoabreu
> https://github.com/apache/incubator-mxnet/issues/10026
>
> cmake cannot build mxnet Bug Build MKL
> #9993 opened 11 days ago by jacky4323
> https://github.com/apache/incubator-mxnet/issues/9993
>
> Flaky hanging test_operator.test_laop_3 @ Python3: MKLDNN-CPU Flaky MKL
> Test
> #9864 opened 21 days ago by marcoabreu
> https://github.com/apache/incubator-mxnet/issues/9864
>
> Flaky test_operator_gpu.test_binary_op @ Python3: MKLDNN-GPU Flaky MKL
> Test
> #9844 opened 23 days ago by marcoabreu
> https://github.com/apache/incubator-mxnet/issues/9844
>
> Building with MKL fails on OSX Build MKL
> #9828 opened 25 days ago by sbodenstein
> https://github.com/apache/incubator-mxnet/issues/9828
>
> MXNET compatibility with MKL libraries bundled in Microsoft R Open MKL
> #8974 opened on Dec 7, 2017 by mjmg
> https://github.com/apache/incubator-mxnet/issues/8974
>
> Intel MKL FATAL ERROR: Cannot load libmkl_avx512_mic.so or libmkl_def.so.
> Bug Data-loading MKL
> #8881 opened on Nov 30, 2017 by wuzhijiexia
> https://github.com/apache/incubator-mxnet/issues/8881
>
> mxnet installation from source: C++ linkage error on HPC C++ Installation
> MKL
> #8874 opened on Nov 30, 2017 by jerrin92
> https://github.com/apache/incubator-mxnet/issues/8874
>
> mxnet-mkl (v0.12.0) crash when using (conda-installed) numpy with MKL Bug
> MKL
> #8532 opened on Nov 3, 2017 by fhieber
> https://github.com/apache/incubator-mxnet/issues/8532
>
>
> > -----Original Message-----
> > From: Zheng, Da [mailto:dzzhen@amazon.com]
> > Sent: Tuesday, March 13, 2018 2:06 AM
> > To: Zhao, Patric <pa...@intel.com>; steffenrochel@gmail.com;
> > dev@mxnet.incubator.apache.org
> > Cc: marco.g.abreu@googlemail.com; Ye, Jason Y <ja...@intel.com>
> > Subject: Re: call for contributions to next MXNet release
> >
> > Patric, thanks for summarizing open issues.
> >
> > Since I'm in the Palo Alto office, maybe we don't need to wait until Apr
> 24th?
> >
> > Best,
> > Da
> >
> > On 3/11/18, 6:43 AM, "Zhao, Patric" <pa...@intel.com> wrote:
> >
> > >- should we talk about the package at the Apr 24th meetup in
> Seattle?
> > We're based in Shanghai, China; so maybe @Da Zheng?
>
>
RE: call for contributions to next MXNet release
Posted by "Zhao, Patric" <pa...@intel.com>.
MKL issues summary:
Feel free to let me know if anything I missed.
Totally, there’re 11 open issues in the github with the label of MKL as below:
4 Bugs issues: #10092, #10086, #10026, #8881
4 Building issues: #9993, #9828, #8974, #8532
1 Flaky Tests: #9864
2 wrong label and invalidated: #9844, #8874
Current status.
3 DONE, to be closed.
4 WIP (working in progress)
2 TODO
2 are invalidated now.
Details:
#10092, WIP, PR#10021
#10086, TODO
#10026, WIP
#9993, DONE (need to be closed), fixed by #10075
#9864, TODO
#9844, INVALIDED, not related w/ MKL
#9828, DONE (need to be closed), fixed by #9918 & #10115
#8974, WIP
#8881, DONE (need to be closed), fixed by #9112
#8874, INVALIDED, “I believe, we are not using MKL”
#8532, WIP, library conflict and can be resolved by environment setting
Lists:
No "full" pooling convention support with MKL-DNN Feature request MKL Operator
#10092 opened 2 days ago by marcoabreu
https://github.com/apache/incubator-mxnet/issues/10092
[MXNET-84] Segfault test_autograd.test_unary_func @ Python3: MKLDNN-CPU Bug MKL Test
#10086 opened 3 days ago by marcoabreu
https://github.com/apache/incubator-mxnet/issues/10086
MXNET_MKLDNN_DEBUG=1 produces errors Bug MKL
#10026 opened 8 days ago by marcoabreu
https://github.com/apache/incubator-mxnet/issues/10026
cmake cannot build mxnet Bug Build MKL
#9993 opened 11 days ago by jacky4323
https://github.com/apache/incubator-mxnet/issues/9993
Flaky hanging test_operator.test_laop_3 @ Python3: MKLDNN-CPU Flaky MKL Test
#9864 opened 21 days ago by marcoabreu
https://github.com/apache/incubator-mxnet/issues/9864
Flaky test_operator_gpu.test_binary_op @ Python3: MKLDNN-GPU Flaky MKL Test
#9844 opened 23 days ago by marcoabreu
https://github.com/apache/incubator-mxnet/issues/9844
Building with MKL fails on OSX Build MKL
#9828 opened 25 days ago by sbodenstein
https://github.com/apache/incubator-mxnet/issues/9828
MXNET compatibility with MKL libraries bundled in Microsoft R Open MKL
#8974 opened on Dec 7, 2017 by mjmg
https://github.com/apache/incubator-mxnet/issues/8974
Intel MKL FATAL ERROR: Cannot load libmkl_avx512_mic.so or libmkl_def.so. Bug Data-loading MKL
#8881 opened on Nov 30, 2017 by wuzhijiexia
https://github.com/apache/incubator-mxnet/issues/8881
mxnet installation from source: C++ linkage error on HPC C++ Installation MKL
#8874 opened on Nov 30, 2017 by jerrin92
https://github.com/apache/incubator-mxnet/issues/8874
mxnet-mkl (v0.12.0) crash when using (conda-installed) numpy with MKL Bug MKL
#8532 opened on Nov 3, 2017 by fhieber
https://github.com/apache/incubator-mxnet/issues/8532
> -----Original Message-----
> From: Zheng, Da [mailto:dzzhen@amazon.com]
> Sent: Tuesday, March 13, 2018 2:06 AM
> To: Zhao, Patric <pa...@intel.com>; steffenrochel@gmail.com;
> dev@mxnet.incubator.apache.org
> Cc: marco.g.abreu@googlemail.com; Ye, Jason Y <ja...@intel.com>
> Subject: Re: call for contributions to next MXNet release
>
> Patric, thanks for summarizing open issues.
>
> Since I'm in the Palo Alto office, maybe we don't need to wait until Apr 24th?
>
> Best,
> Da
>
> On 3/11/18, 6:43 AM, "Zhao, Patric" <pa...@intel.com> wrote:
>
> >- should we talk about the package at the Apr 24th meetup in Seattle?
> We're based in Shanghai, China; so maybe @Da Zheng?
RE: call for contributions to next MXNet release
Posted by "Zhao, Patric" <pa...@intel.com>.
Steffen, really thanks for the helps and I totally agree with you and Marco's suggestions.
I will summarize the open issues and status for the review soon.
> What is your github handle?
Github ID: Patric Zhao, https://github.com/pengzhao-intel/ Da Zheng, https://github.com/zheng-da/
> - do you have design docs we can link to? Does the doc cover packaging, use
> of MXNet with full MKL (I understand there are license issues, but we do have
> users who are or plan to use MXNet with the complete MKL package, not just
> DNN subset)?
Design doc: https://cwiki.apache.org/confluence/display/MXNET/The+design+of+MKLDNN+integration
It's a good suggestion for the full MKL package and we will add the related part in the doc.
> - do you have performance measurements (or plan to measure) to include in
> release notes?
Yes, we have tested the performance on all C4/C5 instances (8x,4x,2x,xlarge,large). And the accuracy are verified as well.
We plan to publish these data both in the release note and mxnet website (https://mxnet.incubator.apache.org/faq/perf.html).
> - should we talk about the package at the Apr 24th meetup in Seattle?
We're based in Shanghai, China; so maybe @Da Zheng?
> -----Original Message-----
> From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> Sent: Sunday, March 11, 2018 6:11 PM
> To: dev@mxnet.incubator.apache.org
> Cc: marco.g.abreu@googlemail.com
> Subject: Re: call for contributions to next MXNet release
>
> Patric - added MKL-DNN to the project list. What is your github handle?
> I do agree with Marco that we need to resolve disable tests, broken features
> etc. Jira looks like the right answer to create a list of known issues.
> Questions I do have:
> - do you have design docs we can link to? Does the doc cover packaging, use
> of MXNet with full MKL (I understand there are license issues, but we do have
> users who are or plan to use MXNet with the complete MKL package, not just
> DNN subset)?
> - do you have performance measurements (or plan to measure) to include in
> release notes?
> - should we talk about the package at the Apr 24th meetup in Seattle?
>
> Steffen
>
> On Sat, Mar 10, 2018 at 4:40 AM Zhao, Patric <pa...@intel.com>
> wrote:
>
> > Hi Marco,
> >
> > Thanks for the inputs.
> >
> > MKL-DNN is just merged to the master branch in a month. I agree that
> > it's not very mature.
> > But, in my mind, there're NO major issues in the current implementation.
> >
> > The previous data race (flaky test) issue is fixed by Zheng Da.
> > We have submitted the PRs to fix the building issues and setup Clang
> > CI environment, such as in OSX and Cmake.
> > Meanwhile, we are actively working on the MXNET for the performance,
> > functionality and usability improvements.
> >
> > More positively, I think we should summarize the open issues, and we
> > can focus on these issues you've mentioned.
> >
> > Thanks,
> >
> > --Patric
> >
> > > -----Original Message-----
> > > From: Marco de Abreu [mailto:marco.g.abreu@googlemail.com]
> > > Sent: Saturday, March 10, 2018 9:36 AM
> > > To: dev@mxnet.incubator.apache.org
> > > Subject: Re: call for contributions to next MXNet release
> > >
> > > Hello Patric,
> > >
> > > please be aware of the fact that there are still a lot of disabled
> > tests, open
> > > MKLDNN issues, broken features and flaky tests that have not been
> > > addressed yet. We agreed on merging MKLDNN for the time being to
> > > allow broad testing and that we will revisit the state a bit before
> > > the next
> > release.
> > > At the moment, I'd not be in favour of having MKLDNN being part of it.
> > >
> > > Best regards,
> > > Marco
> > >
> > > Zhao, Patric <pa...@intel.com> schrieb am Sa., 10. März 2018,
> > 02:30:
> > >
> > > > Hi Steffen,
> > > >
> > > > We'd like the MKL-DNN backend can be included in the next release.
> > > >
> > > > We (Intel engineers) and Zheng-Da (AWS engineer) can work on it.
> > > >
> > > > Could you help add the item in the table?
> > > >
> > > > Thanks,
> > > >
> > > > --Patric
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > > Sent: Friday, March 9, 2018 9:29 PM
> > > > > To: dev@mxnet.incubator.apache.org
> > > > > Subject: call for contributions to next MXNet release
> > > > >
> > > > > Hi - I would like to propose the next MXNet release.
> > > > > Initial draft content is listed at MXNet wiki
> > > > > <https://cwiki.apache.org/confluence/display/MXNET/Project+Propo
> > > > > sals
> > > > > +fo
> > > > > r+next+MXNet+Release>.
> > > > > I would like to call to all contributors to add features you are
> > > > > working
> > > > on and
> > > > > would like to see included in the release. Suggested code freeze
> > > > > is March 30th with target release by mid April.
> > > > >
> > > > > Anirudh Subramanian and Chris Olivier have volunteered to
> > > > > co-manage the release.
> > > > >
> > > > > Mark your date: we are planing public meetup on Apr 24th in Seattle.
> > > > > Details to follow.
> > > > >
> > > > > Regards,
> > > > > Steffen
> > > >
> >
Re: call for contributions to next MXNet release
Posted by Steffen Rochel <st...@gmail.com>.
Patric - added MKL-DNN to the project list. What is your github handle?
I do agree with Marco that we need to resolve disable tests, broken
features etc. Jira looks like the right answer to create a list of known
issues.
Questions I do have:
- do you have design docs we can link to? Does the doc cover packaging, use
of MXNet with full MKL (I understand there are license issues, but we do
have users who are or plan to use MXNet with the complete MKL package, not
just DNN subset)?
- do you have performance measurements (or plan to measure) to include in
release notes?
- should we talk about the package at the Apr 24th meetup in Seattle?
Steffen
On Sat, Mar 10, 2018 at 4:40 AM Zhao, Patric <pa...@intel.com> wrote:
> Hi Marco,
>
> Thanks for the inputs.
>
> MKL-DNN is just merged to the master branch in a month. I agree that it's
> not very mature.
> But, in my mind, there're NO major issues in the current implementation.
>
> The previous data race (flaky test) issue is fixed by Zheng Da.
> We have submitted the PRs to fix the building issues and setup Clang CI
> environment, such as in OSX and Cmake.
> Meanwhile, we are actively working on the MXNET for the performance,
> functionality and usability improvements.
>
> More positively, I think we should summarize the open issues, and we can
> focus on these issues you've mentioned.
>
> Thanks,
>
> --Patric
>
> > -----Original Message-----
> > From: Marco de Abreu [mailto:marco.g.abreu@googlemail.com]
> > Sent: Saturday, March 10, 2018 9:36 AM
> > To: dev@mxnet.incubator.apache.org
> > Subject: Re: call for contributions to next MXNet release
> >
> > Hello Patric,
> >
> > please be aware of the fact that there are still a lot of disabled
> tests, open
> > MKLDNN issues, broken features and flaky tests that have not been
> > addressed yet. We agreed on merging MKLDNN for the time being to allow
> > broad testing and that we will revisit the state a bit before the next
> release.
> > At the moment, I'd not be in favour of having MKLDNN being part of it.
> >
> > Best regards,
> > Marco
> >
> > Zhao, Patric <pa...@intel.com> schrieb am Sa., 10. März 2018,
> 02:30:
> >
> > > Hi Steffen,
> > >
> > > We'd like the MKL-DNN backend can be included in the next release.
> > >
> > > We (Intel engineers) and Zheng-Da (AWS engineer) can work on it.
> > >
> > > Could you help add the item in the table?
> > >
> > > Thanks,
> > >
> > > --Patric
> > >
> > >
> > > > -----Original Message-----
> > > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > > Sent: Friday, March 9, 2018 9:29 PM
> > > > To: dev@mxnet.incubator.apache.org
> > > > Subject: call for contributions to next MXNet release
> > > >
> > > > Hi - I would like to propose the next MXNet release.
> > > > Initial draft content is listed at MXNet wiki
> > > > <https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals
> > > > +fo
> > > > r+next+MXNet+Release>.
> > > > I would like to call to all contributors to add features you are
> > > > working
> > > on and
> > > > would like to see included in the release. Suggested code freeze is
> > > > March 30th with target release by mid April.
> > > >
> > > > Anirudh Subramanian and Chris Olivier have volunteered to co-manage
> > > > the release.
> > > >
> > > > Mark your date: we are planing public meetup on Apr 24th in Seattle.
> > > > Details to follow.
> > > >
> > > > Regards,
> > > > Steffen
> > >
>
RE: call for contributions to next MXNet release
Posted by "Zhao, Patric" <pa...@intel.com>.
Hi Marco,
Thanks for the inputs.
MKL-DNN is just merged to the master branch in a month. I agree that it's not very mature.
But, in my mind, there're NO major issues in the current implementation.
The previous data race (flaky test) issue is fixed by Zheng Da.
We have submitted the PRs to fix the building issues and setup Clang CI environment, such as in OSX and Cmake.
Meanwhile, we are actively working on the MXNET for the performance, functionality and usability improvements.
More positively, I think we should summarize the open issues, and we can focus on these issues you've mentioned.
Thanks,
--Patric
> -----Original Message-----
> From: Marco de Abreu [mailto:marco.g.abreu@googlemail.com]
> Sent: Saturday, March 10, 2018 9:36 AM
> To: dev@mxnet.incubator.apache.org
> Subject: Re: call for contributions to next MXNet release
>
> Hello Patric,
>
> please be aware of the fact that there are still a lot of disabled tests, open
> MKLDNN issues, broken features and flaky tests that have not been
> addressed yet. We agreed on merging MKLDNN for the time being to allow
> broad testing and that we will revisit the state a bit before the next release.
> At the moment, I'd not be in favour of having MKLDNN being part of it.
>
> Best regards,
> Marco
>
> Zhao, Patric <pa...@intel.com> schrieb am Sa., 10. März 2018, 02:30:
>
> > Hi Steffen,
> >
> > We'd like the MKL-DNN backend can be included in the next release.
> >
> > We (Intel engineers) and Zheng-Da (AWS engineer) can work on it.
> >
> > Could you help add the item in the table?
> >
> > Thanks,
> >
> > --Patric
> >
> >
> > > -----Original Message-----
> > > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > > Sent: Friday, March 9, 2018 9:29 PM
> > > To: dev@mxnet.incubator.apache.org
> > > Subject: call for contributions to next MXNet release
> > >
> > > Hi - I would like to propose the next MXNet release.
> > > Initial draft content is listed at MXNet wiki
> > > <https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals
> > > +fo
> > > r+next+MXNet+Release>.
> > > I would like to call to all contributors to add features you are
> > > working
> > on and
> > > would like to see included in the release. Suggested code freeze is
> > > March 30th with target release by mid April.
> > >
> > > Anirudh Subramanian and Chris Olivier have volunteered to co-manage
> > > the release.
> > >
> > > Mark your date: we are planing public meetup on Apr 24th in Seattle.
> > > Details to follow.
> > >
> > > Regards,
> > > Steffen
> >
Re: call for contributions to next MXNet release
Posted by Marco de Abreu <ma...@googlemail.com>.
Hello Patric,
please be aware of the fact that there are still a lot of disabled tests,
open MKLDNN issues, broken features and flaky tests that have not been
addressed yet. We agreed on merging MKLDNN for the time being to allow
broad testing and that we will revisit the state a bit before the next
release. At the moment, I'd not be in favour of having MKLDNN being part of
it.
Best regards,
Marco
Zhao, Patric <pa...@intel.com> schrieb am Sa., 10. März 2018, 02:30:
> Hi Steffen,
>
> We'd like the MKL-DNN backend can be included in the next release.
>
> We (Intel engineers) and Zheng-Da (AWS engineer) can work on it.
>
> Could you help add the item in the table?
>
> Thanks,
>
> --Patric
>
>
> > -----Original Message-----
> > From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> > Sent: Friday, March 9, 2018 9:29 PM
> > To: dev@mxnet.incubator.apache.org
> > Subject: call for contributions to next MXNet release
> >
> > Hi - I would like to propose the next MXNet release.
> > Initial draft content is listed at MXNet wiki
> > <https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+fo
> > r+next+MXNet+Release>.
> > I would like to call to all contributors to add features you are working
> on and
> > would like to see included in the release. Suggested code freeze is March
> > 30th with target release by mid April.
> >
> > Anirudh Subramanian and Chris Olivier have volunteered to co-manage the
> > release.
> >
> > Mark your date: we are planing public meetup on Apr 24th in Seattle.
> > Details to follow.
> >
> > Regards,
> > Steffen
>
RE: call for contributions to next MXNet release
Posted by "Zhao, Patric" <pa...@intel.com>.
Hi Steffen,
We'd like the MKL-DNN backend can be included in the next release.
We (Intel engineers) and Zheng-Da (AWS engineer) can work on it.
Could you help add the item in the table?
Thanks,
--Patric
> -----Original Message-----
> From: Steffen Rochel [mailto:steffenrochel@gmail.com]
> Sent: Friday, March 9, 2018 9:29 PM
> To: dev@mxnet.incubator.apache.org
> Subject: call for contributions to next MXNet release
>
> Hi - I would like to propose the next MXNet release.
> Initial draft content is listed at MXNet wiki
> <https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+fo
> r+next+MXNet+Release>.
> I would like to call to all contributors to add features you are working on and
> would like to see included in the release. Suggested code freeze is March
> 30th with target release by mid April.
>
> Anirudh Subramanian and Chris Olivier have volunteered to co-manage the
> release.
>
> Mark your date: we are planing public meetup on Apr 24th in Seattle.
> Details to follow.
>
> Regards,
> Steffen