29.3. taudb_loadtrial

This utility uploads a trial to the database with a given name, under a specified experiment

$ taudb_loadtrial -h
Usage: perfdmf_loadtrial -a <appName> -x <expName> -n <name> 
[options] <files>

Required Arguments:

  -n, --name <text>              Specify the name of the trial
  -a, --applicationname <string> Specify associated application name
                                 for this trial
  -x, --experimentname <string>  Specify associated experiment name
                                 for this trial

  -n, --name <text>              Specify the name of the trial
  -e, --experimentid <number>    Specify associated experiment ID
                                 for this trial

Optional Arguments:

  -c, --config <name>       Specify the name of the configuration to use
  -g, --configFile <file>   Specify the configuration file to use
                            (overrides -c)
  -f, --filetype <filetype> Specify type of performance data, options 
                            are: profiles (default), pprof, dynaprof, 
                            mpip, gprof, psrun, hpm, packed, cube, 
                            hpc, ompp, snap, perixml, gptl, paraver, 
                            ipm, google
  -t, --trialid <number>    Specify trial ID
  -i, --fixnames            Use the fixnames option for gprof
  -z, --usenull             Include NULL values as 0 for mean 
  -r, --reduce <percentage> Aggregate all timers less than percentage 
                            as "other"
  -m, --metadata <filename> XML metadata for the trial

  For the TAU profiles type, you can specify either a specific set 
of profile files on the commandline, or you can specify a directory 
(by default the current directory).  The specified directory will be 
searched for profile.*.*.* files, or, in the case of multiple counters, 
directories named MULTI_* containing profile data.


  perfdmf_loadtrial -e 12 -n "Batch 001"
    This will load profile.* (or multiple counters directories 
    MULTI_*) into experiment 12 and give the trial the name 
    "Batch 001"

  perfdmf_loadtrial -e 12 -n "HPM data 01" -f hpm perfhpm*
    This will load perfhpm* files of type HPMToolkit into experiment 
    12 and give the trial the name "HPM data 01"

  perfdmf_loadtrial -a "NPB2.3" -x "parametric" -n "64" par64.ppk
    This will load packed profile par64.ppk into the experiment named
    "parametric" under the application named "NPB2.3" and give the 
    trial the name "64".  The application and experiment will be 
    created if not found.

TAUdb supports a large number of parallel profile formats:

  • TAU Profiles (profiles) - Output from the TAU measurement library, these files generally take the form of profile.X.X.X, one for each node/context/thread combination. When multiple counters are used, each metric is located in a directory prefixed with "MULTI__". To launch ParaProf with all the metrics, simply launch it from the root of the MULTI__ directories.

  • ParaProf Packed Format (ppk) - Export format supported by PerfDMF/ParaProf. Typically .ppk.

  • TAU Merged Profiles (snap) - Merged and snapshot profile format supported by TAU. Typically tauprofile.xml.

  • TAU pprof (pprof) - Dump Output from TAU's pprof -d. Provided for backward compatibility only.

  • DynaProf (dynaprof) - Output From DynaProf's wallclock and papi probes.

  • mpiP (mpip) - Output from mpiP.

  • gprof (gprof) - Output from gprof, see also the --fixnames option.

  • PerfSuite (psrun) - Output from PerfSuite psrun files.

  • HPM Toolkit (hpm) - Output from IBM's HPM Toolkit.

  • Cube (cube) - Output from Kojak Expert tool for use with Cube.

  • Cube3 (cube3) - Output from Kojak Expert tool for use with Cube3 and Cube4.

  • HPCToolkit (hpc) - XML data from hpcquick. Typically, the user runs hpcrun, then hpcquick on the resulting binary file.

  • OpenMP Profiler (ompp) - CSV format from the ompP OpenMP Profiler (http://www.ompp-tool.com). The user must use OMPP_OUTFORMAT=CVS.

  • PERI XML (perixml) - Output from the PERI data exchange format.

  • General Purpose Timing Library (gptl) - Output from the General Purpose Timing Library.

  • Paraver (paraver) - 2D output from the Paraver trace analysis tool from BSC.

  • IPM (ipm) - Integrated Performance Monitoring format, from NERSC.

  • Google (google) - Google Profiles.