Proposal for subgraph based the graph optimization and quantization

2018-08-14 Thread Zhao, Patric
Hi MXNet owners and committers,

A new proposal is posted in the wiki for the graph optimization and 
quantization approach.
https://cwiki.apache.org/confluence/display/MXNET/MXNet+Graph+Optimization+and+Quantization+based+on+subgraph+and+MKL-DNN

Really thanks for the supports from Zheng Da and Wu Jun.

Any feedbacks are highly appreciated :)

BR,

--Patric


Re: Release plan - MXNET 1.3

2018-08-14 Thread Roshani Nagmote
Talked to the person who ran resnet50 benchmarks offline. Build flag was
not properly set so there was a difference in performance numbers observed.
There is no issue caught and he was able to get the same results as
mentioned here https://mxnet.incubator.apache.org/faq/perf.html


We are good here.

Thanks,
Roshani

On Mon, Aug 13, 2018 at 4:08 PM Roshani Nagmote 
wrote:

> Hi Dom,
>
> I verified resnet50 run on MXNet master branch. Checked on single gpu
> machine. Numbers match. I didn't see any performance degradation.
> https://mxnet.incubator.apache.org/faq/perf.html#scoring-results
>
> Can you please give me more details on the instance type and script you
> ran exactly so that I can try to reproduce it again?
>
> Thanks,
> Roshani
>
>
> On Mon, Aug 13, 2018 at 12:31 PM Roshani Nagmote <
> roshaninagmo...@gmail.com> wrote:
>
>> This is not a major feature. I meant other new feature requests PR won't
>> be accepted in 1.3 release now.
>> Bug fixes will be accepted. I will be trying to reproduce the regression
>> Dom mentioned today. :)
>>
>> Thanks,
>> Roshani
>>
>> On Mon, Aug 13, 2018 at 12:06 PM Naveen Swamy  wrote:
>>
>>> Is this is a major feature? This is a regression that Dom is reporting
>>> wrt
>>> to performance
>>>
>>> On Mon, Aug 13, 2018 at 11:38 AM, Roshani Nagmote <
>>> roshaninagmo...@gmail.com
>>> > wrote:
>>>
>>> > Thanks for reporting this issue Dom.
>>> > 08/10 (Frida)y was the major feature freeze date. We won't be
>>> accepting any
>>> > new features now for MXNet 1.3 release.
>>> > RC0 will be cut on 08/17(Friday).
>>> >
>>> > Will be verifying the performance degradation issue mentioned.
>>> >
>>> > Thanks,
>>> > Roshani
>>> >
>>> > On Mon, Aug 13, 2018 at 8:45 AM Divakaruni, Dominic
>>> >  wrote:
>>> >
>>> > > Hi all, We tested resnet50 on MXNet built from master branch on
>>> Friday
>>> > and
>>> > > were seeing degraded performance on GPU - about 50% slower compared
>>> to
>>> > > these values here https://mxnet.incubator.apache.org/faq/perf.html.
>>> FWIW
>>> > > this slowdown was seen for both MXNet as well as the TRT integrated
>>> > MXNet.
>>> > >
>>> > > Something for you all to verify before or after you cut the RC.
>>> > >
>>> > > Thx!
>>> > >
>>> > > On 8/13/18, 4:34 AM, "kellen sunderland" <
>>> kellen.sunderl...@gmail.com>
>>> > > wrote:
>>> > >
>>> > > Hey Roshani,
>>> > >
>>> > > Has a RC branch already been cut?  If so, a quick heads up that I
>>> > think
>>> > > this commit should probably get into RC0 for 1.3.
>>> > >
>>> > > https://github.com/apache/incubator-mxnet/commit/
>>> > ee8755a2531b322fec29c9c3d2aa3b8738da41f3
>>> > >
>>> > > It won't cause issues for users, but from a versioning
>>> compatibility
>>> > > perspective it's probably better that we remove these functions
>>> in
>>> > this
>>> > > release. This way we don't have to worry about major bumps in the
>>> > next
>>> > > release if they're removed.
>>> > >
>>> > > -Kellen
>>> > >
>>> > >
>>> > > On Fri, Aug 10, 2018 at 7:24 PM Roshani Nagmote <
>>> > > roshaninagmo...@gmail.com>
>>> > > wrote:
>>> > >
>>> > > > Thanks Kellen and everyone else for working to get TensorRT PR
>>> > > merged!
>>> > > > @Sina, I will be keeping track of that issue and fixes to get
>>> in
>>> > the
>>> > > > release.
>>> > > >
>>> > > > We are starting code freeze for 1.3 release today. A release
>>> > > candidate will
>>> > > > be cut on 08/17.
>>> > > > Feel free to add any other comments/suggestions.
>>> > > >
>>> > > > Thanks,
>>> > > > Roshani
>>> > > >
>>> > > > On Fri, Aug 10, 2018 at 5:39 AM kellen sunderland <
>>> > > > kellen.sunderl...@gmail.com> wrote:
>>> > > >
>>> > > > > All merged and ready to go from my side Roshani (the TensorRT
>>> > PR).
>>> > > > >
>>> > > > > I agree with Sina that issue 12116 looks it's a blocker.
>>> I'll
>>> > try
>>> > > and
>>> > > > > reproduce it locally to get another datapoint.
>>> > > > >
>>> > > > > On Fri, Aug 10, 2018 at 3:15 AM Afrooze, Sina <
>>> > sina@gmail.com>
>>> > > > wrote:
>>> > > > >
>>> > > > > > Hi Roshani - I think this regression issue is a release
>>> > blocker:
>>> > > > > > https://github.com/apache/incubator-mxnet/issues/12116  -
>>> Sina
>>> > > > > >
>>> > > > > >
>>> > > > > > On 8/8/18, 12:40 PM, "Roshani Nagmote" <
>>> > > roshaninagmo...@gmail.com>
>>> > > > > wrote:
>>> > > > > >
>>> > > > > > Thanks, Kellen for letting me know.
>>> > > > > >
>>> > > > > > On Wed, Aug 8, 2018 at 12:09 PM kellen sunderland <
>>> > > > > > kellen.sunderl...@gmail.com> wrote:
>>> > > > > >
>>> > > > > > > Hey Roshani, I think it should be ready by Friday.
>>> > > > > > >
>>> > > > > > > On Tue, Aug 7, 2018, 10:20 PM Roshani Nagmote <
>>> > > > > > roshaninagmo...@gmail.com>
>>>

Consolidating developer guide in one place (cwiki preferred)

2018-08-14 Thread Lin Yuan
Dear MXNet community,

As a developer, I noticed we have some developer guide scattered in
different websites (mxnet.io, cwiki):

E.g.

How to Create New Operators (Layers): [
https://mxnet.incubator.apache.org/faq/new_op.html]
A Guide to Implementing Sparse Operators in MXNet Backend [
https://cwiki.apache.org/confluence/display/MXNET/A+Guide+to+Implementing+Sparse+Operators+in+MXNet+Backend
]

When searching developer guide by keyword, only one of them can be returned
on either site.

It will be more convenient for developers if all the developer guide
resides on cwiki and all user guide (non-developer) on the mxnet.io
website. We can add a link on mxnet.io to refer all developers to cwiki for
guidance.

Any comment is appreciated.

Best Regards,

Lin


Enabling shared filter in JIRA

2018-08-14 Thread Lin Yuan
Dear MXNet Community,

As we are trying to create our Scrum board on JIRA, I noticed that we do
not have the permission to create shared filter, even as an administrator.
This has limited us to create scrum boards for different components of the
project.

I will really appreciate if someone in the Apache Infra team could help to
enable shared filter creation in this project.

Best Regards,

Lin


Re: MXNet Berlin Office Hours

2018-08-14 Thread Ivan Serdyuk
Able to see Carl Tsai online - but can't hear anyone. My webcam is on

On Tue, Aug 14, 2018 at 4:54 PM, Marco de Abreu <
marco.g.ab...@googlemail.com.invalid> wrote:

> Two more hours until we start :)
>
> Ivan Serdyuk  schrieb am Di., 14. Aug. 2018,
> 15:53:
>
> > I am online.
> >
> > On Wed, Aug 8, 2018 at 8:27 PM, Anton Chernov 
> wrote:
> >
> > > Well we are a group of people physically located in Berlin and ready to
> > > provide help in person. A proposal to improve the process is described
> > here
> > > [1]. Any feedback will be greatly appreciated.
> > >
> > > And I just wanted to mention that we had already a few sessions with a
> > lot
> > > of people being happy about the help they got. Sometimes a discussion
> in
> > > person makes a problem so much easier to solve.
> > >
> > > Best
> > > Anton
> > >
> > > [1]
> > > https://cwiki.apache.org/confluence/display/MXNET/
> > > PROPOSAL%3A+Apache+MXNet%28Incubating%29+Office+Hours
> > >
> > > вт, 24 июл. 2018 г. в 4:32, Hen :
> > >
> > > > Noting that I find "MXNet Berlin team" a very confusing concept.
> > > >
> > > > Does that mean "Apache MXNet committers who happen to live in
> Berlin?"
> > > >
> > > > On Mon, Jul 16, 2018 at 2:27 AM, Anton Chernov 
> > > > wrote:
> > > >
> > > > > Dear MXNet community,
> > > > >
> > > > > As part of our customer support the MXNet Berlin team is offering
> > > office
> > > > > hours on Tuesdays 6pm-7pm (CEST) | 9:00am-10am (PST).
> > > > >
> > > > > They happen onsite in the Amazon Berlin office:
> > > > > Krausenstraße 38, 10117 Berlin in BER12 01.501
> > > > >
> > > > > Conference Bridge Information
> > > > >
> > > > > Chime meeting ID: 5461650798
> > > > > Join via browser screen share: https://chime.aws/5461650798
> > > > > Join via phone (US): +1-929-432-4463,,5461650798#
> > > > > Join via phone (US toll-free): +1-855-552-4463,,5461650798#
> > > > > International dial-in: https://chime.aws/dialinnumbers/
> > > > > In-room video system: Ext: 62000, Meeting PIN: 5461650798#
> > > > >
> > > > > How can we help you?
> > > > >
> > > > > The following are a few examples of the types of consultations we
> > > > provide:
> > > > >
> > > > > * CI and infrastructure questions
> > > > > * Build system
> > > > > * Benchmarking
> > > > > * Edge devices (for example Raspberry Pi, Jetson)
> > > > > * C++
> > > > > * General questions
> > > > >
> > > > > Before attending
> > > > >
> > > > > Try finding answers on:
> > > > >
> > > > > * Our discussion forum (https://discuss.mxnet.io)
> > > > > * StackOverflow mxnet tag (https://stackoverflow.com/
> > > > > questions/tagged/mxnet)
> > > > > * MXNet website (https://mxnet.incubator.apache.org/faq/)
> > > > > * Github issues (https://github.com/apache/incubator-mxnet/issues)
> > > > >
> > > > > If this does not help:
> > > > >
> > > > > In advance fill out a github issue (
> > > > > https://github.com/apache/incubator-mxnet/issues/new) at least a
> few
> > > > days
> > > > > before so that the team member who will help with the issue gets a
> > > chance
> > > > > to prepare.
> > > > >
> > > > > Main point of contact through email: mxnet-edge-oncall-primary[at]a
> > > > > mazon.com
> > > > >
> > > > > Best regards
> > > > > Anton Chernov
> > > > >
> > > > > [1]
> > > > > https://cwiki.apache.org/confluence/display/MXNET/
> > > > > MXNet+Berlin+Office+Hours
> > > > >
> > > >
> > >
> >
>


Re: Help with understanding docs

2018-08-14 Thread Isabel Drost-Fromm
On Wed, Aug 08, 2018 at 02:39:22PM -0700, Mu Li wrote:
> > Going through the hosted subdomains that seems not quite correct (or the
> > content hosted is not entirely correct):
> >
> > "Welcome to the MxNet discussion forum." Is what I get as a greeting
> > navigating to discuss.mxnet.io

Am I right with assuming that this is pending evaluation wrt. to capability to
attract new committers and if found useful, something that likely the PMC as a
whole would want control over?


> "This site faciliates data sharing for the MXNet project" is what I get
> > navigating to data.mxnet.io
> 
> This site is deprecated (created before mxnet went to apache), we still
> kept it alive because some old codes may need data from it.

ACK.


> > https://gluon-nlp.mxnet.io/ looks like something you describe. Not sure
> > who exactly is behind it in a legal sense (maybe this helps with
> > understanding where my confusion/worry I coming from for it:
> > https://blogs.apache.org/foundation/entry/success-at-apache-the-apache1 )
> >
> gluon-nlp and gluon-cv are two packaged based on gluon. It's still on early
> developing, we are considering to either donote them to apache or merge
> into mxnet when they are in a more mature sitation. At the same time, we
> are consualting lawyers for the trademark issue, e.g. if gluon is a
> trade-mark owned by Apache.

Meh for the legal hurdles. As for my personal opinion: While a lot of projects
come to Apache through the incubator, I find it easier if projects are pulled
in rather earlier than later.

Especially if you are thinking about merging that into mxnet it sounds like it
would make an aweful lot of sense to keep the Apache mxnet project in the loop
early on.


> > https://zh.mxnet.io ... From what little I understand this looks like
> > some Apache mxnet blog in Chinese?
> >
> > It's a placeholder for the Chinese translated mxnet documents. Currently
> it's just a simple index page.

I know that at least httpd has their docs hosted on their main web page in
multiple languages. Translating docs can be a very low barrier entry for new
contributors. Instead of hosting that on an external site, I think it would
make sense to pull that into the main docs.


> > What I find confusing as well is that at least some of the content looks
> > like it might be official project content (it's even linked to from
> > official project docs), except it seems like it's not controlled by the
> > project?

<- is that assumption correct?


Isabel




Re: MXNet Berlin Office Hours

2018-08-14 Thread Marco de Abreu
Two more hours until we start :)

Ivan Serdyuk  schrieb am Di., 14. Aug. 2018,
15:53:

> I am online.
>
> On Wed, Aug 8, 2018 at 8:27 PM, Anton Chernov  wrote:
>
> > Well we are a group of people physically located in Berlin and ready to
> > provide help in person. A proposal to improve the process is described
> here
> > [1]. Any feedback will be greatly appreciated.
> >
> > And I just wanted to mention that we had already a few sessions with a
> lot
> > of people being happy about the help they got. Sometimes a discussion in
> > person makes a problem so much easier to solve.
> >
> > Best
> > Anton
> >
> > [1]
> > https://cwiki.apache.org/confluence/display/MXNET/
> > PROPOSAL%3A+Apache+MXNet%28Incubating%29+Office+Hours
> >
> > вт, 24 июл. 2018 г. в 4:32, Hen :
> >
> > > Noting that I find "MXNet Berlin team" a very confusing concept.
> > >
> > > Does that mean "Apache MXNet committers who happen to live in Berlin?"
> > >
> > > On Mon, Jul 16, 2018 at 2:27 AM, Anton Chernov 
> > > wrote:
> > >
> > > > Dear MXNet community,
> > > >
> > > > As part of our customer support the MXNet Berlin team is offering
> > office
> > > > hours on Tuesdays 6pm-7pm (CEST) | 9:00am-10am (PST).
> > > >
> > > > They happen onsite in the Amazon Berlin office:
> > > > Krausenstraße 38, 10117 Berlin in BER12 01.501
> > > >
> > > > Conference Bridge Information
> > > >
> > > > Chime meeting ID: 5461650798
> > > > Join via browser screen share: https://chime.aws/5461650798
> > > > Join via phone (US): +1-929-432-4463,,5461650798#
> > > > Join via phone (US toll-free): +1-855-552-4463,,5461650798#
> > > > International dial-in: https://chime.aws/dialinnumbers/
> > > > In-room video system: Ext: 62000, Meeting PIN: 5461650798#
> > > >
> > > > How can we help you?
> > > >
> > > > The following are a few examples of the types of consultations we
> > > provide:
> > > >
> > > > * CI and infrastructure questions
> > > > * Build system
> > > > * Benchmarking
> > > > * Edge devices (for example Raspberry Pi, Jetson)
> > > > * C++
> > > > * General questions
> > > >
> > > > Before attending
> > > >
> > > > Try finding answers on:
> > > >
> > > > * Our discussion forum (https://discuss.mxnet.io)
> > > > * StackOverflow mxnet tag (https://stackoverflow.com/
> > > > questions/tagged/mxnet)
> > > > * MXNet website (https://mxnet.incubator.apache.org/faq/)
> > > > * Github issues (https://github.com/apache/incubator-mxnet/issues)
> > > >
> > > > If this does not help:
> > > >
> > > > In advance fill out a github issue (
> > > > https://github.com/apache/incubator-mxnet/issues/new) at least a few
> > > days
> > > > before so that the team member who will help with the issue gets a
> > chance
> > > > to prepare.
> > > >
> > > > Main point of contact through email: mxnet-edge-oncall-primary[at]a
> > > > mazon.com
> > > >
> > > > Best regards
> > > > Anton Chernov
> > > >
> > > > [1]
> > > > https://cwiki.apache.org/confluence/display/MXNET/
> > > > MXNet+Berlin+Office+Hours
> > > >
> > >
> >
>


Re: MXNet Berlin Office Hours

2018-08-14 Thread Ivan Serdyuk
I am online.

On Wed, Aug 8, 2018 at 8:27 PM, Anton Chernov  wrote:

> Well we are a group of people physically located in Berlin and ready to
> provide help in person. A proposal to improve the process is described here
> [1]. Any feedback will be greatly appreciated.
>
> And I just wanted to mention that we had already a few sessions with a lot
> of people being happy about the help they got. Sometimes a discussion in
> person makes a problem so much easier to solve.
>
> Best
> Anton
>
> [1]
> https://cwiki.apache.org/confluence/display/MXNET/
> PROPOSAL%3A+Apache+MXNet%28Incubating%29+Office+Hours
>
> вт, 24 июл. 2018 г. в 4:32, Hen :
>
> > Noting that I find "MXNet Berlin team" a very confusing concept.
> >
> > Does that mean "Apache MXNet committers who happen to live in Berlin?"
> >
> > On Mon, Jul 16, 2018 at 2:27 AM, Anton Chernov 
> > wrote:
> >
> > > Dear MXNet community,
> > >
> > > As part of our customer support the MXNet Berlin team is offering
> office
> > > hours on Tuesdays 6pm-7pm (CEST) | 9:00am-10am (PST).
> > >
> > > They happen onsite in the Amazon Berlin office:
> > > Krausenstraße 38, 10117 Berlin in BER12 01.501
> > >
> > > Conference Bridge Information
> > >
> > > Chime meeting ID: 5461650798
> > > Join via browser screen share: https://chime.aws/5461650798
> > > Join via phone (US): +1-929-432-4463,,5461650798#
> > > Join via phone (US toll-free): +1-855-552-4463,,5461650798#
> > > International dial-in: https://chime.aws/dialinnumbers/
> > > In-room video system: Ext: 62000, Meeting PIN: 5461650798#
> > >
> > > How can we help you?
> > >
> > > The following are a few examples of the types of consultations we
> > provide:
> > >
> > > * CI and infrastructure questions
> > > * Build system
> > > * Benchmarking
> > > * Edge devices (for example Raspberry Pi, Jetson)
> > > * C++
> > > * General questions
> > >
> > > Before attending
> > >
> > > Try finding answers on:
> > >
> > > * Our discussion forum (https://discuss.mxnet.io)
> > > * StackOverflow mxnet tag (https://stackoverflow.com/
> > > questions/tagged/mxnet)
> > > * MXNet website (https://mxnet.incubator.apache.org/faq/)
> > > * Github issues (https://github.com/apache/incubator-mxnet/issues)
> > >
> > > If this does not help:
> > >
> > > In advance fill out a github issue (
> > > https://github.com/apache/incubator-mxnet/issues/new) at least a few
> > days
> > > before so that the team member who will help with the issue gets a
> chance
> > > to prepare.
> > >
> > > Main point of contact through email: mxnet-edge-oncall-primary[at]a
> > > mazon.com
> > >
> > > Best regards
> > > Anton Chernov
> > >
> > > [1]
> > > https://cwiki.apache.org/confluence/display/MXNET/
> > > MXNet+Berlin+Office+Hours
> > >
> >
>


Re: Requesting slack access

2018-08-14 Thread kellen sunderland
Welcome to MXNet Per.  We're looking forward to having you on the project
(and the team).

On Tue, Aug 14, 2018 at 11:46 AM Marco de Abreu
 wrote:

> Great, welcome to MXNet!
>
> Per da Silva  schrieb am Di., 14. Aug. 2018, 08:29:
>
> > Hi Steffen,
> >
> > Thank you for the warm welcome ^^
> > I'll be joining the AWS AI MXNet team in Berlin later this year. I just
> > wanted to acquaint myself with the code and start contributing before I
> > start.
> > That way I can hit the ground running.
> >
> > Seems like a lot to learn! I'm very excited!
> >
> > Thanks again!
> >
> > Per
> >
> >
> > On Mon, Aug 13, 2018 at 6:10 PM Steffen Rochel 
> > wrote:
> >
> > > Hi Per - added you to slack. Welcome to the project and looking forward
> > to
> > > collaborate. Please use also discuss.mxnet.io to ask questions.
> > > What are you working on?
> > >
> > > Regards,
> > > Steffen
> > >
> > > On Mon, Aug 13, 2018 at 6:31 AM Per da Silva 
> > wrote:
> > >
> > > > Hi,
> > > >
> > > > I would like to have access to your slack channel.
> > > >
> > > > Thank you,
> > > >
> > > > Per
> > > >
> > >
> >
>


Re: Requesting slack access

2018-08-14 Thread Marco de Abreu
Great, welcome to MXNet!

Per da Silva  schrieb am Di., 14. Aug. 2018, 08:29:

> Hi Steffen,
>
> Thank you for the warm welcome ^^
> I'll be joining the AWS AI MXNet team in Berlin later this year. I just
> wanted to acquaint myself with the code and start contributing before I
> start.
> That way I can hit the ground running.
>
> Seems like a lot to learn! I'm very excited!
>
> Thanks again!
>
> Per
>
>
> On Mon, Aug 13, 2018 at 6:10 PM Steffen Rochel 
> wrote:
>
> > Hi Per - added you to slack. Welcome to the project and looking forward
> to
> > collaborate. Please use also discuss.mxnet.io to ask questions.
> > What are you working on?
> >
> > Regards,
> > Steffen
> >
> > On Mon, Aug 13, 2018 at 6:31 AM Per da Silva 
> wrote:
> >
> > > Hi,
> > >
> > > I would like to have access to your slack channel.
> > >
> > > Thank you,
> > >
> > > Per
> > >
> >
>