RE: [Announce] Upcoming Apache MXNet (incubating) 1.4.0 release
Thanks, Steffen. I think there is NO open issue to block the MKLDNN to GA now. BTW, several quantization related PRs (#13297,#13260) are under the review and I think it can be merged in this week. Thanks, --Patric > -Original Message- > From: Steffen Rochel [mailto:steffenroc...@gmail.com] > Sent: Tuesday, November 20, 2018 2:57 AM > To: dev@mxnet.incubator.apache.org > Subject: Re: [Announce] Upcoming Apache MXNet (incubating) 1.4.0 release > > On Friday the contributors working on Java API discovered a potential > performance problem with inference using Java API vs. Python. Investigation > is ongoing. > As the Java API is one of the main features for the upcoming release, I > suggest to post-pone the code freeze towards end of this week. > > Please provide feedback and concern about the change in dates for code > freeze and 1.4.0 release. I will provide updates on progress resolving the > potential performance problem. > > Patrick - do you think it is possible to resolve the remaining issues on MKL- > DNN this week, so we can consider GA for MKL-DNN with 1.4.0? > > Regards, > Steffen > > On Thu, Nov 15, 2018 at 5:26 AM Anton Chernov > wrote: > > > I'd like to remind everyone that 'code freeze' would mean cutting a > > v1.4.x release branch and all following fixes would need to be backported. > > Development on master can be continued as usual. > > > > Best > > Anton > > > > ср, 14 нояб. 2018 г. в 6:04, Steffen Rochel : > > > > > Dear MXNet community, > > > the agreed plan was to establish code freeze for 1.4.0 release > > > today. As the 1.3.1 patch release is still ongoing I suggest to > > > post-pone the code freeze to Friday 16th November 2018. > > > > > > Sergey Kolychev has agreed to act as co-release manager for all > > > tasks > > which > > > require committer privileges. If anybody is interested to volunteer > > > as release manager - now is the time to speak up. Otherwise I will > > > manage > > the > > > release. > > > > > > Regards, > > > Steffen > > > > >
Re: [Announce] Upcoming Apache MXNet (incubating) 1.4.0 release
+1 to wait until Java API work is ready since it is a major feature of the release, yet performance should be at least on par with Python. Also, I consider the MKL-DNN feature to be another major feature of the release, the performance boost on CPU is significant [1], as an example, ResNet50-v1 is 15.9x faster on C5.18xlarge. I spoke with Alex Zai and Manu Seth who are working on MKL-DNN issues and test coverage, and they feel they can get all remaining open issues in for this Friday - I propose we also wait for that work to be ready and included in 1.4.0 Cheers, Hagay [1] https://cwiki.apache.org/confluence/display/MXNET/MXNet+with+Intel+MKL-DNN+-+Performance+Benchmarking On Mon, Nov 19, 2018 at 10:57 AM Steffen Rochel wrote: > On Friday the contributors working on Java API discovered a potential > performance problem with inference using Java API vs. Python. Investigation > is ongoing. > As the Java API is one of the main features for the upcoming release, I > suggest to post-pone the code freeze towards end of this week. > > Please provide feedback and concern about the change in dates for code > freeze and 1.4.0 release. I will provide updates on progress resolving the > potential performance problem. > > Patrick - do you think it is possible to resolve the remaining issues on > MKL-DNN this week, so we can consider GA for MKL-DNN with 1.4.0? > > Regards, > Steffen > > On Thu, Nov 15, 2018 at 5:26 AM Anton Chernov wrote: > > > I'd like to remind everyone that 'code freeze' would mean cutting a > v1.4.x > > release branch and all following fixes would need to be backported. > > Development on master can be continued as usual. > > > > Best > > Anton > > > > ср, 14 нояб. 2018 г. в 6:04, Steffen Rochel : > > > > > Dear MXNet community, > > > the agreed plan was to establish code freeze for 1.4.0 release today. > As > > > the 1.3.1 patch release is still ongoing I suggest to post-pone the > code > > > freeze to Friday 16th November 2018. > > > > > > Sergey Kolychev has agreed to act as co-release manager for all tasks > > which > > > require committer privileges. If anybody is interested to volunteer as > > > release manager - now is the time to speak up. Otherwise I will manage > > the > > > release. > > > > > > Regards, > > > Steffen > > > > > >
Re: [Announce] Upcoming Apache MXNet (incubating) 1.4.0 release
On Friday the contributors working on Java API discovered a potential performance problem with inference using Java API vs. Python. Investigation is ongoing. As the Java API is one of the main features for the upcoming release, I suggest to post-pone the code freeze towards end of this week. Please provide feedback and concern about the change in dates for code freeze and 1.4.0 release. I will provide updates on progress resolving the potential performance problem. Patrick - do you think it is possible to resolve the remaining issues on MKL-DNN this week, so we can consider GA for MKL-DNN with 1.4.0? Regards, Steffen On Thu, Nov 15, 2018 at 5:26 AM Anton Chernov wrote: > I'd like to remind everyone that 'code freeze' would mean cutting a v1.4.x > release branch and all following fixes would need to be backported. > Development on master can be continued as usual. > > Best > Anton > > ср, 14 нояб. 2018 г. в 6:04, Steffen Rochel : > > > Dear MXNet community, > > the agreed plan was to establish code freeze for 1.4.0 release today. As > > the 1.3.1 patch release is still ongoing I suggest to post-pone the code > > freeze to Friday 16th November 2018. > > > > Sergey Kolychev has agreed to act as co-release manager for all tasks > which > > require committer privileges. If anybody is interested to volunteer as > > release manager - now is the time to speak up. Otherwise I will manage > the > > release. > > > > Regards, > > Steffen > > >
collecting anonymous statistics
Hi folks As you know we have a combinatorial explosion of build flavours and different libraries / platforms / environments. Is collecting and gathering anonymous usage statistics as it's done in other open source projects something which would be acceptable for the community? I think it would help us understand where to put efforts and how different features are being used. Regards. Pedro.
CUDNN Install Link
Hello All, Does anyone have a solution for downloading CUDNN from the command line? Its currently behind an authorization process on the website and I am trying to automate the MXNet dependency installs. The version I am trying to install is v7.4.1 CUDA 9.2 for Windows 10 (ideally windows server 2016). https://devtalk.nvidia.com/default/topic/1002046/cuda-setup-and-installation/download-cudnn-via-wget-or-curl-/ Chance Bair
Re: [VOTE] Release Apache MXNet (incubating) version 1.3.1.rc0
+1 from me (macOS) > On Nov 16, 2018, at 2:52 AM, kellen sunderland > wrote: > > Thanks for organizing the release Anton and for testing Carin and Steffen. > Lots of great fixes in this release. As we don't have the required 3 > committers I'd suggest extending the vote for a few days. > > I tested the following on MacOS 10.13, High Sierra: > > INCUBATING IN RELEASE FILE: check. > LICENSE check. > NOTICE check. > SIGNATURE check. > HASH check. > DISCLAIMER check. > SOURCE COMPILES VIA MAKEFILE check. > SOURCE COMPILES VIA CMAKE check. > C++ TESTS PASS fail > Two tests failing for me. > Build with flags: cmake -DUSE_CUDA=0 -DUSE_CUDNN=0 -DUSE_OPENMP=0 > -DUSE_OPENCV=0 .. > Ran c++ tests with exclusions: ./tests/mxnet_unit_tests > --gtest_filter=-GpuTopology.* > Result: > [ FAILED ] 2 tests, listed below: > [ FAILED ] ACTIVATION_PERF.ExecuteBidirectional > [ FAILED ] ACTIVATION_PERF.TimingCPU > > PYHTON UNIT TESTS PASS check. > > Not sure if the test failures are a regression so I'm +0 (non-binding) > > On Thu, Nov 15, 2018 at 5:43 PM Steffen Rochel > wrote: > >> +1 build on MacOS Sierra following instructions on >> >> https://cwiki.apache.org/confluence/display/MXNET/MXNet+Developer+Setup+on+Mac >> and run one training test. >> >> On Tue, Nov 13, 2018 at 2:34 PM Carin Meier wrote: >> >>> +1 - Clojure package tested fine with Scala jars >>> >>> On Mon, Nov 12, 2018 at 6:53 PM Anton Chernov >> wrote: >>> Dear MXNet community, This is the vote to release Apache MXNet (incubating) version 1.3.1. >>> Voting will start now, on Monday the 12th of November 2018 and close on 14:00 Thursday the 15th of November 2018, Pacific Time (PT). Link to release notes: https://cwiki.apache.org/confluence/x/eZGzBQ Link to release candidate 1.3.1.rc0: https://github.com/apache/incubator-mxnet/releases/tag/1.3.1.rc0 Link to source and signatures on apache dist server: https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.3.1.rc0/ Link to scala packages on the staging repo: * CPU >>> >> https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-osx-x86_64-cpu/1.3.1-SNAPSHOT/ * GPU >>> >> https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-linux-x86_64-gpu/1.3.1-SNAPSHOT/ Please remember to TEST first before voting accordingly: +1 = approve +0 = no opinion -1 = disapprove (provide reason) Best regards, Anton >>> >>
