Last modified 14 years ago Last modified on 05/19/09 16:23:38


Performance Database for FLASH

If TAU was used to collect the performance data, a number of profile.* files are generated upon successful execution. You can load the profiles into an existing database by following these steps:

Java program to load TAU profiles and Metadata.

The CQoSDataLoader program is a wrapper around perfdmf_loadtrial - it loads the performance data, and it also puts the metadata in the metadata_parameters table.

A Java program to load the TAU profiles and associated metadata is here:

You run it like this:

java -jar CQoSDataLoader_fat.jar

and with the parameters:

java -jar CQoSDataLoader_fat.jar -a 10 -t trial -c database_name -d results_directory

For example:

java -jar CQoSDataLoader_fat.jar -a FLASH_Sedov -t p64 -c FLASH_DB -d $HOME/FLASH3/exec
  • Usage notes
    • For the CQoSDataLoader program (and perfdmf_loadtrial, for that matter), you specify the application & experiment NAMES, not the IDs.
    • perfdmf_createapp and perfdmf_createxp are old programs that should be removed - you shouldn't use them.
  • When you call the loader with no parameters, it will give you the help message:
    java -jar CQoSDataLoader_fat.jar
    Usage: dataLoader -d <directory> -c <config>
          -d --directory    directory with TAU profiles and metadata.txt file
          -c --config       PerfDMF configuration
          -a --application  application name
          -e --experiment   experiment name
          -t --trial        trial name
    where 'config' is the postfix of a PerfDMF configuration file with the full path: $HOME/.ParaProf/perfdmf.cfg.postfix Internally, the TAU tools will assume and pre-pend the "$HOME/.ParaProf/perfdmf.cfg." part.