The DAGDA configuration options

DAGDA introduces new configuration options that can be defined for all the DAGDA components. None of these options are mandatory to use DAGDA. Figure 16.2 presents all the DAGDA available options, their meaning and default values.
Figure 16.2: DAGDA configuration options



Default value

The directory on which DAGDA will store the data files

The /tmp directory.
52 52 52

The maximum size of a CORBA message sent by DAGDA.

The omniORB giopMaxMsgSize size.
52 52 52

The maximum disk space used by DAGDA to store the data. If set to 0, DAGDA will not take care of the disk usage.

The available disk space on the disk partition chosen by the storageDirectory option.
52 52 52

The maximum memory space used by DAGDA to store the data. If set to 0, DAGDA will not take care of the memory usage.

No maximum memory usage is set. Same effect than to choose 0.
52 52 52

The cache replacement algorithm used when DAGDA needs more space to store a data. Possible values are: LRU, LFU, FIFO

No cache replacement algorithm. DAGDA never replace a data by another one.
52 52 52

The DAGDA component shares its file data with all its children (when the path is accessible by them, for example, if the storage directory is on a NFS partition). Value can be 0 or 1.

No file sharing - 0
56 52 56

The path to the file that will be used when DAGDA save all its stored data/data path when asked by the user (Checkpointing).

No checkpointing is possible.
56 52 52

DAGDA will load the dataBackupFile file at start and restore all the data recorded at the last checkpointing event. Possible values are 0 or 1.

No file loading on start - 0
56 52 52

The DIET Team - Mer 29 nov 2017 15:13:36 EST