Changes between Version 39 and Version 40 of WikiStart
- Timestamp:
- 01/13/12 15:40:13 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v39 v40 28 28 * `UsedKe` 29 29 30 When monitoring per task each task writes the value for each key to the file `.memlog/task<MPI-rank>.log` and waits for the next time step. When monitoring by node the process running on core 0 of each node writes the value for each key to the file `node<node-name>_task<MPI-task>.log`. 30 When monitoring per task each task writes the value for each key to the file `.memlog/task<MPI-rank>.log` and waits for the next time step. When monitoring by node the process running on core 0 of each node writes the value for each key to the file `node<node-name>_task<MPI-task>.log`. Both (monitoring by task and monitoring by node) can be active at the same time. 31 31 32 After the run is finished the analyzer `juman` is run in the `PBS_O_WORKDIR`, either from within the same job script or afterwards on the login node to analyze the consumed resources. It will create graphs with the value of key (default: `VmSize`, => `key`, option `-k`) for each task at each time step (use `juman -k help` for a list of available keys), the process with the maximum value of the key at each time step and the total sum of all values of a key across all tasks at each time step (=> `statistics`, option `-s`). If `-i` is specified the graphs are displayed immediately.32 The data produced by `jumel` can be analyzed by the `juman` script which performs statistical analysis of the data (minimum, maximum and total sum of values) and generates corresponding graphs. 33 33 34 34 == Usage == … … 39 39 juman -u 40 40 }}} 41 42 Defaults:43 * work directory: `.memlog`44 * delay: 10 seconds45 * all ranks log the memory consumption46 * resources logged: `/proc/<id>/status: VmSize, VmRSS, VmData, VmStk`47 41 48 42 Suppose the application to monitor is started usually as follows: … … 56 50 57 51 {{{ 58 mpiexec -np 32 -e PBS_ID,APP_ROOT jumel - a "app.x -i app.inp" > my.out52 mpiexec -np 32 -e PBS_ID,APP_ROOT jumel -n -a "app.x -i app.inp" > my.out 59 53 }}} 60 54 … … 62 56 63 57 {{{ 64 juman -s all - i58 juman -s all -n -i 65 59 }}} 66 60 67 The -s option switches on the statistics (currently: total consumption and maximum consumption per time step) and the `-i` option will start the graphical display of the results. Currently only a `gnuplot` interface is implemented and postscript of`xfig` files can be generated. An interface for visualization with Python is planned.61 The -s option switches on the statistics and the `-i` option will start the graphical display of the results. Currently only a `gnuplot` interface is implemented and postscript or `xfig` files can be generated. An interface for visualization with Python is planned. 68 62 69 63 == Example: Namd == … … 78 72 module load namd/2.7 79 73 80 mpiexec -np 32 -e PBS_JOBID jumel - a "$NAMD_ROOT/bin/namd2 apoa1.namd"74 mpiexec -np 32 -e PBS_JOBID jumel -n -p -t -a "$NAMD_ROOT/bin/namd2 apoa1.namd" 81 75 82 76 }}} … … 85 79 86 80 {{{ 87 juman -s all - i81 juman -s all -n -t -i 88 82 }}} 89 83 … … 104 98 105 99 106 mpiexec -np 16 jumel -d 2 - a "mapt.x" > mapt.out100 mpiexec -np 16 jumel -d 2 -n -p -t -a "mapt.x" > mapt.out 107 101 108 102 }}} … … 111 105 112 106 {{{ 113 juman -s all -i 107 juman -s all -i -n -t 114 108 }}} 115 109
