Yes and no re the dependency. Without async_modex, the cutoff will save you memory footprint but not result in any launch performance benefit. Likewise, turning on async_modex without being over the cutoff won't do you any good as you'll immediately demand all the modex data.
So they are kinda related, but not in a rigid sense. Maybe they should be...? On Thu, Feb 4, 2016 at 9:31 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > On Feb 4, 2016, at 9:18 AM, Ralph Castain <r...@open-mpi.org> wrote: > > > > +1, with an addition and modification: > > > > * add the async_modex on by default > > * make the change in master and let it "stew" for awhile before moving > to 2.0. I believe only Cisco has been running MTT against that setup so far. > > It's been a little while, and I forget exactly what the async modex is -- > can you refresh my memory? > > I'd be ok with enabling the async_modex, but that's not dependency to or > from this 1024->32 change, right? I.e., does the "enable async_modex" > change need to be tied to this change? > > Regardless, I'm fine letting this stuff cook on master for a little bit > before PR'ing to v2.x. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/02/18554.php >
