RE: Include MKLDNN into default mxnet pip package

2018-11-21 Thread Lv, Tao A
Thanks for the information, Kellen and Naveen. Better than onnx-tensorrt, MKL-DNN has already provided versioning and release tags. My concern is that as MKL-DNN is still under intensive development, if it has a new feature or bug fix on its master branch, do we really want to wait for next

Re: Include MKLDNN into default mxnet pip package

2018-11-21 Thread kellen sunderland
Agree with your point about other repos also not being based on versioning Tao. I would point out that I've given some that I've worked with similar feedback: https://github.com/onnx/onnx-tensorrt/issues/68 On Wed, Nov 21, 2018 at 6:48 PM Naveen Swamy wrote: > Tao, > > You are right there are

Re: Include MKLDNN into default mxnet pip package

2018-11-21 Thread Naveen Swamy
Tao, You are right there are many submodules in 3rd party. We have to start somewhere and I believe this one is a good candidate to start with. This is not to cater to release of MXNet or to tie them with the releases of the submodules but instead to pick only stable releases and not to pick up

RE: Include MKLDNN into default mxnet pip package

2018-11-21 Thread Zhao, Patric
Hi Kellen, Thank you very much for your recognition for our works :) This is a great joint work from the community (Wu Jun, Zheng Da, etc.) and Intel team. We are continuously improving the quantization flow now and more amazing features will be ready soon. Thanks, --Patric >

RE: Include MKLDNN into default mxnet pip package

2018-11-21 Thread Lv, Tao A
Here are my answers for the questions from Kellen and Naveen about MKL-DNN. It doesn't mean that I'm supportive for making MKL-DNN default here. @Kellen, FYI, here is a list for those platforms which are officially supported by MKL-DNN. https://github.com/intel/mkl-dnn#system-requirements

Re: Include MKLDNN into default mxnet pip package

2018-11-21 Thread kellen sunderland
I've spent the last few days testing MXNet w/ MKLDNN and quantized models and it's a beast. Really good speed improvements on my models, no bugs that I've noticed. I'm in general supportive but I'm still wondering what the story is like when there's no AVX instructions present on CPUs. Do we

Re: Include MKLDNN into default mxnet pip package

2018-11-21 Thread Zai, Alexander
AMD benchmarks have been published. We are seeing a x15.8 speedup with Resnet50 (batch size 32) on AWS's new m5a.24xlarge machine. With a smaller network (Mobilenet - batch size 32) the speedup is more significant at x38.7. Let's have a vote to see if the PR to have MKLDNN enabled by default

Re: CI impaired

2018-11-21 Thread Qing Lan
Appreciated for your effort and help to make CI a better place! Qing On 11/21/18, 4:38 PM, "Lin Yuan" wrote: Thanks for your efforts, Marco! On Wed, Nov 21, 2018 at 4:02 PM Anirudh Subramanian wrote: > Thanks for the quick response and mitigation! > > On

Re: CI impaired

2018-11-21 Thread Marco de Abreu
Hello, today, CI had some issues and I had to cancel all jobs a few minutes ago. This was basically caused by the high load that is currently being put on our CI system due to the pre-release efforts for this Friday. It's really unfortunate that we just had outages of three core components

Re: Splitting Jenkins pipelines - stop changes to Jenkinsfiles!

2018-11-21 Thread Anirudh
Hi Marco, Can you point out specifically which checks we have to make sure pass before merging PRs. Currently apart from the required one there are six steps added. Also, is the CI down currently :

Re: A New API for creating .rec files

2018-11-21 Thread Anirudh Acharya
Hi All, Sorry for the delay, but here is the design spec for the API - https://cwiki.apache.org/confluence/display/MXNET/Image+Transforms+and+RecordIO+file+Creation Look forward to feedback from the community. Regards Anirudh On Tue, Sep 25, 2018 at 2:15 PM kellen sunderland <

Re: CI impaired

2018-11-21 Thread Gavin M Bell
Yes, let me add to the kudos, very nice work Marco. "I'm trying real hard to be the shepherd." -Jules Winnfield > On Nov 21, 2018, at 5:04 PM, Sunderland, Kellen > wrote: > > Appreciate the big effort in bring the CI back so quickly. Thanks Marco. > > On Nov 21, 2018 5:52 AM, Marco de

Re: CI impaired

2018-11-21 Thread Sunderland, Kellen
Appreciate the big effort in bring the CI back so quickly. Thanks Marco. On Nov 21, 2018 5:52 AM, Marco de Abreu wrote: Thanks Aaron! Just for the record, the new Jenkins jobs were unrelated to that incident. If somebody is interested in the details around the outage: Due to a required

Re: [RESULTS] [VOTE] Release Apache MXNet (incubating) version 1.3.1.rc0

2018-11-21 Thread Anton Chernov
The vote on the @general list of incubator.apache.org has been started: https://lists.apache.org/thread.html/adf86e1c3332559ad91880a412aa1063dc72cd6f4f3d6c4c0d91a2dd@%3Cgeneral.incubator.apache.org%3E The vote closes on 24th of November 2018 14:30 CET. Best Anton вт, 20 нояб. 2018 г. в

Re: Splitting Jenkins pipelines - stop changes to Jenkinsfiles!

2018-11-21 Thread Marco de Abreu
Hello, the PR has been merged and I've created the new pipelines at [1]. You can see the new reports if you have a look at this example PR at [2]. The new status messages will be the ones starting with "ci/jenkins/mxnet-validation/". This now allows you to retrigger specific pipelines if they

Re: CI impaired

2018-11-21 Thread Marco de Abreu
Thanks Aaron! Just for the record, the new Jenkins jobs were unrelated to that incident. If somebody is interested in the details around the outage: Due to a required maintenance (disk running full), we had to upgrade our Jenkins master because it was running on Ubuntu 17.04 (for an unknown

Re: CI impaired

2018-11-21 Thread Aaron Markham
Marco, thanks for your hard work on this. I'm super excited about the new Jenkins jobs. This is going to be very helpful and improve sanity for our PRs and ourselves! Cheers, Aaron On Wed, Nov 21, 2018, 05:37 Marco de Abreu Hello, > > the CI is now back up and running. Auto scaling is working

Re: CI impaired

2018-11-21 Thread Marco de Abreu
Hello, the CI is now back up and running. Auto scaling is working as expected and it passed our load tests. Please excuse the caused inconveniences. Best regards, Marco On Wed, Nov 21, 2018 at 5:24 AM Marco de Abreu wrote: > Hello, > > I'd like to let you know that our CI was impaired and