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 rel
On Feb 4, 2016, at 9:18 AM, Ralph Castain 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
+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.
On Thu, Feb 4, 2016 at 6:04 AM, Gilles Gouaillardet <
gilles.gouaillar...
+1
should we also enable sparse groups by default ?
(or at least on master, and then v2.x later)
Cheers,
Gilles
On Thursday, February 4, 2016, Joshua Ladd wrote:
> +1
>
>
> On Wed, Feb 3, 2016 at 9:54 PM, Jeff Squyres (jsquyres) <
> jsquy...@cisco.com >
> wrote:
>
>> WHAT: Decrease default va
+1
On Wed, Feb 3, 2016 at 9:54 PM, Jeff Squyres (jsquyres)
wrote:
> WHAT: Decrease default value of mpi_add_procs_cutoff from 1024 to 32
>
> WHY: The "partial add procs" behavior is supposed to be a key feature of
> v2.0.0
>
> WHERE: ompi/mpi/runtime/ompi_mpi_params.c
>
> TIMEOUT: Next Tuesday
WHAT: Decrease default value of mpi_add_procs_cutoff from 1024 to 32
WHY: The "partial add procs" behavior is supposed to be a key feature of v2.0.0
WHERE: ompi/mpi/runtime/ompi_mpi_params.c
TIMEOUT: Next Tuesday teleconf (9 Feb 2016)
MORE DETAIL:
The mpi_add_procs_cutoff MCA param controls th
