1
1
openmpi/orte/mca/state
Ralph Castain 8f496b01b7 Try automatically adding local spawn threads to parallelize the fork/exec process to speed up the launch on large SMPs. Harvest the threads after initial spawn to minimize any impact on running jobs.
Change the determination of #spawn threads to be done on basis of #local procs in first job being spawned. Someone can look at an optimization that handles subsequent dynamic spawns that might be larger in size.

Leave the threads running, but blocked, for the life of the daemon, and use them to harvest the local procs as they terminate. This helps short-lived jobs in particular.

Add MCA params to set:
  * max number of spawn threads (default: 4)
  * set a specific number of spawn threads (default: -1, indicating no set number)
  * cutoff - minimum number of local procs before using spawn threads (default: 32)

Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2017-11-29 19:54:00 -08:00
..
app mca: Dynamic components link against project lib 2017-08-24 11:56:16 -04:00
base Enable remote tool connections for the DVM. Fix notifications so we "de-bounce" termination calls 2017-10-06 10:47:05 -07:00
dvm Add support for the -v (verbose) option to prun and silence the "executing" and "completed" output otherwise. 2017-10-10 12:54:49 -07:00
hnp Enable remote tool connections for the DVM. Fix notifications so we "de-bounce" termination calls 2017-10-06 10:47:05 -07:00
novm mca: Dynamic components link against project lib 2017-08-24 11:56:16 -04:00
orted Try automatically adding local spawn threads to parallelize the fork/exec process to speed up the launch on large SMPs. Harvest the threads after initial spawn to minimize any impact on running jobs. 2017-11-29 19:54:00 -08:00
tool mca: Dynamic components link against project lib 2017-08-24 11:56:16 -04:00
Makefile.am Purge whitespace from the repo 2015-06-23 20:59:57 -07:00
state_types.h Purge whitespace from the repo 2015-06-23 20:59:57 -07:00
state.h Instead of "forced_terminate" just quietly causing the daemon to disappear, let's at least attempt to let the user know where the problem occurred. 2017-06-02 08:28:16 -07:00