0411f9772e
I have added a new MCA param (hey, you can't have too many!) called OMPI_MCA_orte_timing. If set to anything other than zero, the system will report out critical timing loops. At the moment, this includes three measurements: 1. Time spent going through the RDS->RAS->RMAPS, setting up triggers, etc. prior to calling the actual PLS launch function. This is reported out as time to setup job. 2. Time spent in MPI_Init from start of that function (well, right after opal_init) to the place where we send all of our info the registry. Reported out as time from start to exec_compound_cmd 3. Time actually spent executing the compound cmd. Reported out as time to exec_compound_cmd. A few additional timing points will be added shortly. These may eventually be removed or (better) setup with a conditional compile flag. This commit was SVN r11892. |
||
---|---|---|
.. | ||
help-mpi-runtime.txt | ||
Makefile.am | ||
mpiruntime.h | ||
ompi_mpi_abort.c | ||
ompi_mpi_finalize.c | ||
ompi_mpi_init.c | ||
ompi_mpi_io.c | ||
ompi_mpi_params.c | ||
ompi_mpi_preconnect.c | ||
params.h |