Re: [apache/incubator-mxnet] [RFC][mxnet 2.0][item 10.1] MXNet Imperative Op Invocation Overhead (#17097)

[Haozheng Fan]

I created a follow-up design proposal on 
[cwiki](https://cwiki.apache.org/confluence/display/MXNET/MXNet+FFI+for+Operator+Imperative+Invocation).
 TVM FFI works well with MXNet and the overhead for `np.zeros` gets greatly 
reduced. Any feedback is appreciated.

-- 
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17097#issuecomment-578011639

Proposal: MXNet FFI for Operator Imperative Invocation

[Fan, Haozheng]

Hi MXNet Community,

The MXNet slow FFI has been a known issue for quite some time. In a recent RFC 
[1] we reached a consensus that TVM FFI is a fast and suitable replacement. 
Here is a follow-up design proposal [2] and a POC [3]. Feedbacks are welcome.

Thank you,
MXNet developers from AWS

[1] RFC https://github.com/apache/incubator-mxnet/issues/17097
[2] Design Proposal
https://cwiki.apache.org/confluence/display/MXNET/MXNet+FFI+for+Operator+Imperative+Invocation
[3] POC https://github.com/hzfan/incubator-mxnet/pull/2

Re: MXNet 1.6 as last release with Python 2 support?

[Lausen, Leonard]

pip 20 install issues will likely be fixed by upstream tomorrow: 
https://github.com/pypa/pip/issues/7626#issuecomment-577860648

On Thu, 2020-01-23 at 15:13 -0800, Pedro Larroy wrote:
>  This is not good user experience. I have heard of impacts to some users /
> projects.
> 
> Thanks.
> 
> On Tue, Jan 21, 2020 at 10:44 PM Skalicky, Sam 
> wrote:
> 
> > Also, it has been reported that pip wheel installation with latest pip
> > version 20.0.1 breaks installation of MXNet pip wheels which have py2.py3
> > in the wheel name. This breaks all existing released versions. Work around
> > is to install the older version of pip "pip install pip==19.3.1”.
> > 
> > Sam
> > 
> > > On Jan 21, 2020, at 4:35 PM, Chung, Alex 
> > wrote:
> > > +1
> > > 
> > > Sincerely,
> > > 
> > > Alex Chung
> > > Senior Product Manager | AWS AI
> > > 
> > > 
> > > From: shiwen hu 
> > > Sent: Tuesday, January 21, 2020 4:26 PM
> > > To: dev@mxnet.incubator.apache.org
> > > Subject: Re: MXNet 1.6 as last release with Python 2 support?
> > > 
> > > +1
> > > 
> > > Lai Wei  于2020年1月18日周六 上午2:51写道：
> > > 
> > > > +1
> > > > 
> > > > 
> > > > Best Regards
> > > > 
> > > > Lai
> > > > 
> > > > 
> > > > On Fri, Jan 17, 2020 at 10:39 AM Lin Yuan  wrote:
> > > > 
> > > > > +1
> > > > > 
> > > > > On Fri, Jan 17, 2020 at 10:04 AM Xingjian SHI 
> > > > > wrote:
> > > > > 
> > > > > > +1. We should move to support Python>=3.5 only.
> > > > > > 
> > > > > > Get Outlook for iOS
> > > > > > 
> > > > > > From: Lausen, Leonard 
> > > > > > Sent: Friday, January 17, 2020 10:02:30 AM
> > > > > > To: d...@mxnet.apache.org 
> > > > > > Subject: Re: MXNet 1.6 as last release with Python 2 support?
> > > > > > 
> > > > > > If the lazy consensus passes, I believe the minimum Python version
> > > > > > supported
> > > > > > would be Python 3.5.
> > > > > > 
> > > > > > Python 3.5 because it seems to be the minimum Python 3 version
> > > > > > tested
> > > > by
> > > > > > our CI,
> > > > > > specifically in the jobs running on Ubuntu 16.04.
> > > > > > 
> > > > > > Best regards
> > > > > > Leonard
> > > > > > 
> > > > > > On Fri, 2020-01-17 at 17:36 +, Lausen, Leonard wrote:
> > > > > > > Dear MXNet community,
> > > > > > > 
> > > > > > > as effective January 1, 2020, no new bug reports, fixes, or
> > > > > > > changes
> > > > > will
> > > > > > be
> > > > > > > made
> > > > > > > to Python 2, and as MXNet 1.6 will be released after January 1,
> > > > 2020, I
> > > > > > > suggest
> > > > > > > to announce in the MXNet 1.6 release notes that MXNet 1.6 is the
> > > > > > > last
> > > > > > release
> > > > > > > supporting Python 2.
> > > > > > > 
> > > > > > > We have previously reached consensus on announcing that Python 2
> > > > > > > is
> > > > > > dropped in
> > > > > > > the next major release (ie. MXNet 2), however, given the delay in
> > > > > > > 1.6
> > > > > > release,
> > > > > > > the plan to release 1.7 in the future and that Python 2 is dead
> > > > > already I
> > > > > > > think
> > > > > > > we can revisit this assumption.
> > > > > > > 
> > > > > > > Advantages are
> > > > > > > - Time savings for developers, as Python 3 standard library
> > > > > > > contains
> > > > > more
> > > > > > >  features than Python 2, and it is more efficient to target only 1
> > > > > > language
> > > > > > >  (Python 3) instead of 2 languages (Python 2 & 3)
> > > > > > > - Simplification and cost savings for CI
> > > > > > > 
> > > > > > > I thus suggest 72h lazy consensus for announcing dropping of
> > > > > > > Python 2
> > > > > as
> > > > > > > described above. If you disagree, please veto (send "-1") and we
> > > > > > > can
> > > > > > continue
> > > > > > > supporting Python 2 in all 1.x releases as per previous consensus.
> > > > Note
> > > > > > that
> > > > > > > at
> > > > > > > the time of previous consensus, no 1.7 release was planned.
> > > > > > > 
> > > > > > > Best regards
> > > > > > > Leonard

Re: MXNet 1.6 as last release with Python 2 support?

[Pedro Larroy]

 This is not good user experience. I have heard of impacts to some users /
projects.

Thanks.

On Tue, Jan 21, 2020 at 10:44 PM Skalicky, Sam 
wrote:

> Also, it has been reported that pip wheel installation with latest pip
> version 20.0.1 breaks installation of MXNet pip wheels which have py2.py3
> in the wheel name. This breaks all existing released versions. Work around
> is to install the older version of pip "pip install pip==19.3.1”.
>
> Sam
>
> > On Jan 21, 2020, at 4:35 PM, Chung, Alex 
> wrote:
> >
> > +1
> >
> > Sincerely,
> >
> > Alex Chung
> > Senior Product Manager | AWS AI
> >
> > 
> > From: shiwen hu 
> > Sent: Tuesday, January 21, 2020 4:26 PM
> > To: dev@mxnet.incubator.apache.org
> > Subject: Re: MXNet 1.6 as last release with Python 2 support?
> >
> > +1
> >
> > Lai Wei  于2020年1月18日周六 上午2:51写道：
> >
> >> +1
> >>
> >>
> >> Best Regards
> >>
> >> Lai
> >>
> >>
> >> On Fri, Jan 17, 2020 at 10:39 AM Lin Yuan  wrote:
> >>
> >>> +1
> >>>
> >>> On Fri, Jan 17, 2020 at 10:04 AM Xingjian SHI 
> >>> wrote:
> >>>
>  +1. We should move to support Python>=3.5 only.
> 
>  Get Outlook for iOS
>  
>  From: Lausen, Leonard 
>  Sent: Friday, January 17, 2020 10:02:30 AM
>  To: d...@mxnet.apache.org 
>  Subject: Re: MXNet 1.6 as last release with Python 2 support?
> 
>  If the lazy consensus passes, I believe the minimum Python version
>  supported
>  would be Python 3.5.
> 
>  Python 3.5 because it seems to be the minimum Python 3 version tested
> >> by
>  our CI,
>  specifically in the jobs running on Ubuntu 16.04.
> 
>  Best regards
>  Leonard
> 
>  On Fri, 2020-01-17 at 17:36 +, Lausen, Leonard wrote:
> > Dear MXNet community,
> >
> > as effective January 1, 2020, no new bug reports, fixes, or changes
> >>> will
>  be
> > made
> > to Python 2, and as MXNet 1.6 will be released after January 1,
> >> 2020, I
> > suggest
> > to announce in the MXNet 1.6 release notes that MXNet 1.6 is the last
>  release
> > supporting Python 2.
> >
> > We have previously reached consensus on announcing that Python 2 is
>  dropped in
> > the next major release (ie. MXNet 2), however, given the delay in 1.6
>  release,
> > the plan to release 1.7 in the future and that Python 2 is dead
> >>> already I
> > think
> > we can revisit this assumption.
> >
> > Advantages are
> > - Time savings for developers, as Python 3 standard library contains
> >>> more
> >  features than Python 2, and it is more efficient to target only 1
>  language
> >  (Python 3) instead of 2 languages (Python 2 & 3)
> > - Simplification and cost savings for CI
> >
> > I thus suggest 72h lazy consensus for announcing dropping of Python 2
> >>> as
> > described above. If you disagree, please veto (send "-1") and we can
>  continue
> > supporting Python 2 in all 1.x releases as per previous consensus.
> >> Note
>  that
> > at
> > the time of previous consensus, no 1.7 release was planned.
> >
> > Best regards
> > Leonard
> 
> >>>
> >>
>
>