Re: [ANNOUNCE] MKLDNN becomes the default CPU backend in Apache/MXNet master branch
Awesome work! On Sat, Jan 12, 2019 at 1:25 AM Lv, Tao A wrote: > Thanks for the great collaboration through the community to make things > happen. :) > > > -Original Message- > From: Jun Wu [mailto:wujun@gmail.com] > Sent: Saturday, January 12, 2019 12:54 PM > To: dev@mxnet.incubator.apache.org > Cc: u...@mxnet.apache.org > Subject: Re: [ANNOUNCE] MKLDNN becomes the default CPU backend in > Apache/MXNet master branch > > Great work on boosting the MXNet/MKLDNN performance significantly! > > On Fri, Jan 11, 2019 at 7:08 PM Li, Mu wrote: > > > Awesome job! That’s a great benefit to CPU users > > > > Best > > Mu > > > > > On Jan 11, 2019, at 6:59 PM, Zhao, Patric > wrote: > > > > > > Dear all, > > > > > > I am pleased to announce that the MKLDNN is the default CPU backend in > > the master branch for the Linux platform now. > > > (note: the nightly build and release doesn't change) > > > > > > Really thanks to the great supports and joint works from the community. > > > > > > Feedbacks are highly appreciated :) > > > > > > Related links: > > > > > > 1. Integration design: > > > https://cwiki.apache.org/confluence/display/MXNET/The+design+of+MKLDNN+integration > > > > > > 2. Performance and accuracy: > > > https://cwiki.apache.org/confluence/display/MXNET/MXNet+with+Intel+MKL-DNN+-+Performance+Benchmarking > > > > > > 3. MKLDNN README: > > https://github.com/apache/incubator-mxnet/blob/master/MKLDNN_README.md > > > > > > Thanks, > > > > > > --Patric > > > > > >
Re: Question about notification on nightly test failures
Thanks for the explanation Marco :) - Carin On Sat, Jan 12, 2019 at 7:43 PM Marco de Abreu wrote: > Hi Carin, > > thanks for thinking about adding nightly tests to clojure, I'm sure this > will be of big benefit! > > You're right, the email system is in place but we basically disabled the > service December 2017 because it was flooding the inboxes of everybody. > > We've been thinking about various notification methods, but were always > afraid making the notifications meaningless if they come too frequently > (which is WAY better now, thanks to everybody's efforts around stabilizing > the tests!) because people would filter them. > > I like the idea of a specific slack channel for the notifications. Are > there any alternatives the community could think of? > > Best regards, > Marco > > > Am Sa., 12. Jan. 2019, 10:11 hat Carin Meier > geschrieben: > > > The Clojure package is thinking of adding some nightly tests and I'd like > > to understand how the notification works in case of failure. > > > > The code in the nightly Jenkins file > > > > > https://github.com/apache/incubator-mxnet/blob/master/tests/nightly/Jenkinsfile#L135 > > seems to indicate that the failure is emailed. But where does this email > > go? > > If you are a contributor, do you get notified of this? > > > > I don't remember seeing any notification of nightly failures, so I'm > > wondering how this works and if there are any improvements to > accessibility > > that we can make, (like maybe posting it to a slack room)? > > > > Thanks, > > Carin > > >
Re: Question about notification on nightly test failures
Hi Carin, thanks for thinking about adding nightly tests to clojure, I'm sure this will be of big benefit! You're right, the email system is in place but we basically disabled the service December 2017 because it was flooding the inboxes of everybody. We've been thinking about various notification methods, but were always afraid making the notifications meaningless if they come too frequently (which is WAY better now, thanks to everybody's efforts around stabilizing the tests!) because people would filter them. I like the idea of a specific slack channel for the notifications. Are there any alternatives the community could think of? Best regards, Marco Am Sa., 12. Jan. 2019, 10:11 hat Carin Meier geschrieben: > The Clojure package is thinking of adding some nightly tests and I'd like > to understand how the notification works in case of failure. > > The code in the nightly Jenkins file > > https://github.com/apache/incubator-mxnet/blob/master/tests/nightly/Jenkinsfile#L135 > seems to indicate that the failure is emailed. But where does this email > go? > If you are a contributor, do you get notified of this? > > I don't remember seeing any notification of nightly failures, so I'm > wondering how this works and if there are any improvements to accessibility > that we can make, (like maybe posting it to a slack room)? > > Thanks, > Carin >
RE: [ANNOUNCE] MKLDNN becomes the default CPU backend in Apache/MXNet master branch
Thanks for the great collaboration through the community to make things happen. :) -Original Message- From: Jun Wu [mailto:wujun@gmail.com] Sent: Saturday, January 12, 2019 12:54 PM To: dev@mxnet.incubator.apache.org Cc: u...@mxnet.apache.org Subject: Re: [ANNOUNCE] MKLDNN becomes the default CPU backend in Apache/MXNet master branch Great work on boosting the MXNet/MKLDNN performance significantly! On Fri, Jan 11, 2019 at 7:08 PM Li, Mu wrote: > Awesome job! That’s a great benefit to CPU users > > Best > Mu > > > On Jan 11, 2019, at 6:59 PM, Zhao, Patric wrote: > > > > Dear all, > > > > I am pleased to announce that the MKLDNN is the default CPU backend in > the master branch for the Linux platform now. > > (note: the nightly build and release doesn't change) > > > > Really thanks to the great supports and joint works from the community. > > > > Feedbacks are highly appreciated :) > > > > Related links: > > > > 1. Integration design: > https://cwiki.apache.org/confluence/display/MXNET/The+design+of+MKLDNN+integration > > > > 2. Performance and accuracy: > https://cwiki.apache.org/confluence/display/MXNET/MXNet+with+Intel+MKL-DNN+-+Performance+Benchmarking > > > > 3. MKLDNN README: > https://github.com/apache/incubator-mxnet/blob/master/MKLDNN_README.md > > > > Thanks, > > > > --Patric > > >
