Changes between Version 16 and Version 17 of WikiStart


Ignore:
Timestamp:
08/15/11 16:00:46 (13 years ago)
Author:
Florian Janetzko
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v16 v17  
    1212  * `VmStk`
    1313  * `VmRSS`
    14 Each task writes the value for each key in the file .memlog/task<MPI-rank>.log and waits for the next time step.
     14Each task writes the value for each key in the file `.memlog/task<MPI-rank>.log` and waits for the next time step.
    1515
    16 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 (see option -s). If -i is specified the graphs are displayed immediately.
     16After 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.
    1717
    1818== Usage ==
    … …  
    2020
    2121{{{
    22 jumel -u
    23 juman -u
     22`jumel -u`
     23`juman -u`
    2424}}}
    2525
    2626Defaults:
    27   * work directory: .memlog
     27  * work directory: `.memlog`
    2828  * delay: 10 seconds
    2929  * all ranks log the memory consumption
    30   * resources logged: /proc/<id>/status: Vm Size, Vm RSS, Vm Data, Vm Stk
     30  * resources logged: `/proc/<id>/status: VmSize, VmRSS, VmData, VmStk`
    3131
    3232Suppose the application to monitor is started usually as follows:
    … …  
    4343}}}
    4444
    45 The variable PBS_ID needs not to be specified, how ever it will be displayed in the jumel logfiles and eases the tracking of the runs afterwards (e.g. when looking for the job in the system logfiles). Once the run is finished run juman in the same directory:
     45The variable `PBS_ID` needs not to be specified, how ever it will be displayed in the `jumel` logfiles and eases the tracking of the runs afterwards (e.g. when looking for the job in the system logfiles). Once the run is finished run `juman` in the same directory:
    4646
    4747{{{
    … …  
    4949}}}
    5050
    51 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.
     51The -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.
    5252
    5353== Example: Namd ==
    … …  
    6666}}}
    6767
    68 The graphs were optained afterwards on the login node with
     68The graphs were obtained afterwards on the login node with
    6969
    7070{{{