+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 <steffenroc...@gmail.com> 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 <mecher...@gmail.com> 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 <steffenroc...@gmail.com>: > > > > > 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 > > > > > >
