Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread Jeff Squyres (jsquyres)
Yeah, just like Artem, I had forgotten about this repo (until I went to go look to create a new repo). :-) > On Aug 26, 2016, at 11:46 AM, George Bosilca wrote: > > As your name appear inside (not on commits thou) I though you knew about that > repo, so I was confused on why do you want anot

Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread George Bosilca
As your name appear inside (not on commits thou) I though you knew about that repo, so I was confused on why do you want another one. ;) George. On Fri, Aug 26, 2016 at 10:36 AM, Jeff Squyres (jsquyres) < jsquy...@cisco.com> wrote: > Cool. Let me know if you need anything else. > > > > On Au

Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread Jeff Squyres (jsquyres)
Cool. Let me know if you need anything else. > On Aug 26, 2016, at 10:34 AM, Artem Polyakov wrote: > > Sufficient. Probably I missed it. No need to do anything. > > 2016-08-26 21:31 GMT+07:00 Jeff Squyres (jsquyres) : > Just curious: is https://github.com/open-mpi/2016-summer-perf-testing not

Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread Artem Polyakov
Sufficient. Probably I missed it. No need to do anything. 2016-08-26 21:31 GMT+07:00 Jeff Squyres (jsquyres) : > Just curious: is https://github.com/open-mpi/2016-summer-perf-testing not > sufficient? > > > > > On Aug 26, 2016, at 10:28 AM, Artem Polyakov wrote: > > > > I'd prefer it to be creat

Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread Jeff Squyres (jsquyres)
Just curious: is https://github.com/open-mpi/2016-summer-perf-testing not sufficient? > On Aug 26, 2016, at 10:28 AM, Artem Polyakov wrote: > > I'd prefer it to be created. > > 2016-08-26 20:59 GMT+07:00 Jeff Squyres (jsquyres) : > Sorry for jumping in so late. > > Honestly, there's no prob

Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread Artem Polyakov
I'd prefer it to be created. 2016-08-26 20:59 GMT+07:00 Jeff Squyres (jsquyres) : > Sorry for jumping in so late. > > Honestly, there's no problem with making a repo in the open-mpi github > org. It's just as trivial to make one there as anywhere else. > > Let me know if you want one. > > > > On

Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread Jeff Squyres (jsquyres)
Sorry for jumping in so late. Honestly, there's no problem with making a repo in the open-mpi github org. It's just as trivial to make one there as anywhere else. Let me know if you want one. > On Aug 26, 2016, at 8:46 AM, Artem Polyakov wrote: > > I've marked the first week. > > 2016-08-2

Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread Artem Polyakov
I've marked the first week. 2016-08-26 19:26 GMT+07:00 George Bosilca : > Let's go regular for a period and then adapt. > > For everybody interested in the performance discussion, I setup a doodle > for next week. The dates themselves are not important, we need a regular > timeslot. Please answer

Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread George Bosilca
Let's go regular for a period and then adapt. For everybody interested in the performance discussion, I setup a doodle for next week. The dates themselves are not important, we need a regular timeslot. Please answer with the idea that we do 4 weeks in a row and then assess the situation and dece i

Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread Artem Polyakov
This is a good idea. We also have data with SM/Vader to discuss. I'll send them later this week. Do you think of regular calls or per agreement? пятница, 26 августа 2016 г. пользователь George Bosilca написал: > We are serious about this. However, we not only have to define a set of > meaningful

Re: [OMPI devel] Performance analysis proposal

2016-08-26 Thread George Bosilca
We are serious about this. However, we not only have to define a set of meaningful tests (which we don't have yet) but also decide the conditions in which they are executed, and more critically what additional information we need to make them reproducible, understandable and comparable. We started