Re: Formalize Committer Proposal and Application Procedure

that high bar. This is difficult to quantify but is a quality that is expected to be demonstrated in various conversations of the person being nominated to be the committer. Bhavin Thaker. On Wed, Aug 9, 2017 at 11:03 PM, Sebastian <s...@apache.org> wrote: > > Another thing might be that hav

Re: Integrating a forum with the mailing lists for better usability

+1 On Fri, Sep 15, 2017 at 4:45 PM Naveen Swamy wrote: > + 1 > > On Fri, Sep 15, 2017 at 4:32 PM, Vikram Madan > wrote: > > > +1 > > > > On Fri, Sep 15, 2017 at 3:40 PM, Lupesko, Hagay > wrote: > > > > > +1 > > > > > > I think

Re: PROCESS: Contacting the Apache Infra team

to learn from the mistakes of other Apache projects and also contribute to that guidelines list. Later, we can propose our guidelines page to contribute back to the *main Apache guidelines page for incubating projects*. Bhavin Thaker. On Thu, Oct 5, 2017 at 10:24 PM, Sebastian <ss

Re: What's everyone working on?

Hi Seb: please use a different email thread for new topics of discussion. Hi Jun: I think Seb may be referring to Volta V100 support in MXNet and NOT P4/P40 inference accelerators. Corrections/clarifications welcome. Bhavin Thaker. On Mon, Oct 2, 2017 at 8:22 PM Jun Wu <wujun@gmail.

Re: Improving and rationalizing unit tests

MXNet (Incubating). Regards, Bhavin Thaker. On Mon, Oct 16, 2017 at 5:56 AM Pedro Larroy <pedro.larroy.li...@gmail.com> wrote: > Hi > > Some of the unit tests are extremely costly in terms of memory and compute. > > As an example in the gluon tests we a

Re: proposal to shut down apache-mxnet.slack.com

+1 to disable old slack, but keep old messages viewable. Bhavin Thaker. On Mon, Oct 16, 2017 at 8:23 AM Steffen Rochel <steffenroc...@gmail.com> wrote: > As we have now migrated the majority of people from apache-mxnet.slack.com > to the-asf.slack.com I would like to suggest

Re: Improving and rationalizing unit tests

failures for PRs. There are other places (nightly) to do extensive tests. PR-unit-tests are sanity tests and must be quick, reliable and consistent for every PR. Bhavin Thaker. On Mon, Oct 16, 2017 at 8:51 AM Pedro Larroy <pedro.larroy.li...@gmail.com> wrote: > That's not true. random() an

Re: Jira and/or feature collision

one feature > > On Mon, Sep 11, 2017 at 5:30 PM, Bhavin Thaker <bhavintha...@gmail.com> > wrote: > > > +1 : Chris has an important question. > > > > How do we ensure that a feature/task for a particular Apache project is > not > > worked on by multiple

Re: Jira and/or feature collision

is working on what. Bhavin Thaker. On Mon, Sep 11, 2017 at 5:06 AM Joern Kottmann <kottm...@gmail.com> wrote: > A good way to coordinate is to use the dev list and/or state on the > issues that you are interested in it and are working on it. > > We use Jira for years at Apac

Re: MXNet: Run PR builds on Apache Jenkins only after the commit is reviewed

-review and only after sufficient amount of sanity build-tests have passed. Let the machines work harder for humans and not the other way around. Bhavin Thaker. On Tue, Sep 12, 2017 at 12:20 PM Chris Olivier <cjolivie...@gmail.com> wrote: > The majority of these iterations is to trigge

Re: PROCESS: Contacting the Apache Infra team

Hi John, I went through the mentioned section and scanned the entire page. It is very helpful. Thanks! Regards, Bhavin Thaker. On Fri, Oct 6, 2017 at 4:32 PM, John D. Ament <johndam...@apache.org> wrote: > Bhavin, > > You may want to review http://www.apache.org/dev/infra-

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

T use GPU context on a CPU-only instance. Bhavin Thaker. On Sun, Nov 26, 2017 at 7:01 PM, Steffen Rochel <steffenroc...@gmail.com> wrote: > +1 (non-binding) > verified building from source and tested on macOS Sierra > > On Sun, Nov 26, 2017 at 10:32 AM Chris Olivier &

Re: Futex

. https://stackoverflow.com/questions/6364314/why-is-a-pthread-mutex-considered-slower-than-a-futex Bhavin Thaker. On Thu, Nov 23, 2017 at 10:00 PM kellen sunderland < kellen.sunderl...@gmail.com> wrote: > I think Haitao is right given some stacks we've recently looked at. e.g

Re: Futex

Do we have performance/profiling measurement evidence to prove/disprove the claims of the impact of mutex bottleneck in MXNet? Bhavin Thaker. On Thu, Nov 23, 2017 at 11:03 AM Tianqi Chen <tqc...@cs.washington.edu> wrote: > If they are not bottleneck. Then resorting to standard library

Re: [VOTE] A Separate CI System for Apache MXNet (incubating)

+1 for [1] Jenkins (A setup separated from Apache Jenkins) - with various plugins. Bhavin Thaker. On Fri, Nov 10, 2017 at 11:39 AM, Madan Jampani <madan.jamp...@gmail.com> wrote: > +1 for (1) > > On Thu, Nov 9, 2017 at 4:41 PM, Meghna Baijal <meghnabaijal2...@gmail.com>

Re: [DISCUSSION] Adding labels to PRs

+1 for better [1] PR Titles. As suggested by Madan and use by Spark, the current PR template seems to be ignored by folks and so we may want to simplify it to: Q1. What changes were proposed in this pull request? Q2. How was this patch tested? +1 to either [2] Jira OR [3] PR labels. Bhavin

Re: update build instructions

I agree about your point on correctness -- do you know of any known correctness issues with Ninja? These build times seem to be NOT with GPU builds and distributed kvstore enabled -- could you please confirm? nvcc builds take a significant time. Bhavin Thaker. On Thu, Nov 2, 2017 at 8:45 AM

Re: [Proposal] Stabilizing Apache MXNet CI build system

, what is the expected SLA for a response from them? When users deploy MXNet in production environments, they will expect some form of SLA for support and a patch release. Regards, Bhavin Thaker. On Wed, Nov 1, 2017 at 8:20 AM, Pedro Larroy <pedro.larroy.li...@gmail.com> wrote: > +1 T

Re: update build instructions

-build.org/manual.html Thanks, Bhavin Thaker. On Thu, Nov 2, 2017 at 7:57 AM, Pedro Larroy <pedro.larroy.li...@gmail.com> wrote: > Hi > > I would like to update the MXNet build instructions. > > In particular I was thinking that it would be a good idea to update > the i

Re: Move to new CI

Hi Marco, Thanks for your work on the CI. Is it possible/ok to share the docs via googledocs link until you get write permissions for the apache wiki page? Bhavin Thaker. On Tue, Dec 5, 2017 at 4:06 PM, Marco de Abreu <marco.g.ab...@googlemail.com > wrote: > Hello MXNet

Re: segmentation fault in master using mkdlnn

Have you tried running with valgrind to get some clues on the root-cause? Bhavin Thaker. On Wed, May 2, 2018 at 8:55 PM Da Zheng <zhengda1...@gmail.com> wrote: > It might also be possible that this isn't an MKLDNN bug. > I just saw a similar memory error without MKLDNN bui

Re: segmentation fault in master using mkdlnn

to reproduce the crash and then use Valgrind to get to the culprit portion of the code quickly. Bhavin Thaker. On Thu, May 3, 2018 at 6:49 AM Pedro Larroy <pedro.larroy.li...@gmail.com> wrote: > It's very difficult to reproduce, non-deterministic. We were also running > without signal handl

Re: Apache MXNet Development Processes: Proposed update

://cwiki.apache.org/confluence/display/MXNET/Development+Process Wishing all of you a very happy new year 2018! Regards, Bhavin Thaker. On Fri, Dec 22, 2017 at 12:36 AM, kellen sunderland < kellen.sunderl...@gmail.com> wrote: > Sheng’s comments are correct. GitHub will save review

Re: CUDA Support [DISCUSS]

/incubator-mxnet/issues/8805 Bhavin Thaker. On Sat, Jan 6, 2018 at 3:30 AM kellen sunderland < kellen.sunderl...@gmail.com> wrote: > Hello all, I'd like to propose that we nail down exactly which versions of > CUDA we're supporting. We can then ensure that we've got good test > cov

Re: CUDA Support [DISCUSS]

that the MXNet CI run tests only with latest CUDA9 version and NOT CUDA8. I am eager to hear alternate viewpoints/corrections from folks other than Kellen and me. Bhavin Thaker. On Sat, Jan 6, 2018 at 8:24 AM kellen sunderland < kellen.sunderl...@gmail.com> wrote: > Thanks for the though

Re: CUDA Support [DISCUSS]

to the open-source Apache MXNet. Bhavin Thaker. On Sat, Jan 6, 2018 at 12:30 PM Naveen Swamy <mnnav...@gmail.com> wrote: > +1 to that. I think we don't have to run CUDA 8 on every PR. > > On Sat, Jan 6, 2018 at 12:26 PM, Marco de Abreu < > marco.g.ab...@googlemail.com>

Re: [Discussion] Branch Usage and Release Versioning

. In short, your proposal #3 is good and ideal but seems less practical based on my observations so far. Bhavin Thaker. On Thu, Jan 18, 2018 at 12:58 AM Marco de Abreu < marco.g.ab...@googlemail.com> wrote: > Hi Sheng, > > very good suggestions! How long do we plan to suppo

Re: Call for Help for Fixing Flaky Tests

instead of doing it during the upcoming release. Bhavin Thaker. On Sat, Jan 13, 2018 at 2:20 PM, Marco de Abreu < marco.g.ab...@googlemail.com> wrote: > Hello Sheng, > > thanks a lot for leading this task! > > +1 for both points. Additionally, I'd propose to add the req

Re: [DISCUSSION] Adding labels to PRs

+1 to having committers act as role models for descriptive PR title and descriptions. I am sorry to say this explicitly because I found a few committers to have no descriptions in their PRs with PR titles that seemed vague to me as a contributor of Apache MXNet. Bhavin Thaker. On Sun, Jan 14

Re: [DISCUSSION] Adding labels to PRs

documented here (prepared after the MXNet 1.0 Release): https://cwiki.apache.org/confluence/display/MXNET/Release+Retrospective+for+Apache+MXNet+%28incubating%29+1.0.0 Any comments or suggestion on the above Release retrospective are most welcome. Bhavin Thaker. On Mon, Nov 13, 2017 at 3:03 PM

Re: R Build failure

Ok, Marco. Do all the permitted datasets reside in S3 or is this a todo item? Bhavin Thaker. On Fri, Jan 12, 2018 at 7:28 AM Marco de Abreu <marco.g.ab...@googlemail.com> wrote: > It would make sense, but the license does not permit redistribution of the > GroupLens-Movie dataset

Re: R Build failure

Does it make sense to cache the datasets into a (reliable) S3 bucket so the tests to run reliably? Does the dataset licensing allow downloading the dataset? Bhavin Thaker. On Fri, Jan 12, 2018 at 5:52 AM kellen sunderland < kellen.sunderl...@gmail.com> wrote: > Hey all, since this ser

Re: Reduce 99% of your memory leaks with this simple trick!

Would it make sense to have a developer best practices section on the Apache wiki where such guidance can be documented for future reference? Bhavin Thaker. On Thu, Jan 11, 2018 at 9:56 AM Anirudh <anirudh2...@gmail.com> wrote: > Hi, > > > I have been thinking about

Re: Podling Report Reminder - January 2018

on various MXNet talks at conferences, universities, etc. If anybody has suggestions on how to increase the contributions to MXNet, please share your ideas. Bhavin Thaker. On Tue, Jan 2, 2018 at 9:15 PM Hen <bay...@apache.org> wrote: > Few items that flagged for me in the report: &g

Suggestions on how to increase community involvement on Apache MXNet incubating?

questions in the one question above, I am looking for more ideas or thoughts. Cheers, Bhavin Thaker.

Re: Podling Report Reminder - January 2018

. Thanks, Bhavin Thaker. On Wed, Jan 3, 2018 at 10:39 AM, Hen <bay...@apache.org> wrote: > Thanks Bhavin. Let's definitely get that as an active conversation. > > In general I'm okay with the report. I'm having login pains with the wiki > (yay for non-ldap service), but chatted with S

Re: GCC march flags and target architecture in x86-64, remove -msse2

017 # AVX_to_SSE_instances/100instructions: 0.1687 # SSE_to_AVX_instances/100instructions: 0.1687 Bhavin Thaker. On Mon, Aug 13, 2018 at 7:00 AM Pedro Larroy wrote: > Hi > > I think we should explicitly define march to be x86-64 (which is the > default in Linux) and documented here: > h

Re: S3 Writes using SIG4 Authentication

Multi-part upload with finalization seems like a good approach for this problem. Bhavin Thaker. On Wed, Mar 7, 2018 at 7:45 AM Naveen Swamy <mnnav...@gmail.com> wrote: > Rahul, > IMO It is not Ok to write to a local file before streaming, you have to > consider securi

Re: Wiki Access

Done. On Mon, Mar 12, 2018 at 11:27 AM Chris Olivier wrote: > Can someone please give write me access to the MXNet wiki? >

Re: S3 Writes using SIG4 Authentication

ote that this is also efficient because local memory or disk I/O (assuming SSD or high-grade rotating hard disk) will be faster than multiple S3 put calls over long-distance network. Bhavin Thaker. On Tue, Mar 6, 2018 at 10:34 PM Rahul Huilgol <rahulhuil...@gmail.com> wrote: > Hi Chris, &g