Update the tuning configuration overrides

CD_RUN_TASKLIST_AS_INSTANCES

Tasks are stored procedures that implement a certain function. For example, the gqValidation task will validate gas quality (GQ) records.

All of the tasks are placed in the taskList table and processed according to how long they have been waiting.

An instance calls all the procedures that are required to process a row in the correct order.

For example, for hourlyGasAnalysis, it will call the associated tasks in the following order:

• Data collection routines

• Validation routines

• Post-processing routines

When CD_RUN_TASKLIST_AS_INSTANCES is enabled, the interval of the first task in the instance will determine when the instance will be run. taskList average wait statistics will only be updated for this first task.

Enabling this configDesc setting has been found to increase throughput on test and development systems. However, depending on the profile of data entering into the system, it also has the potential to decrease throughput.

When changing this setting, we recommend that you test the performance before and after the change to determine if the system is performing better or worse. Changes to this setting will take effect at the next startup.

To enable this, configure the following setting:

Set the booleanValue for CD_RUN_TASKLIST_AS_INSTANCES to Y.

CD_THROTTLE

The CD_THROTTLE setting is used to define the maximum amount of rows in the operationRequestQueue.

Once this has been exceeded, estimation and data collection will pause until the rows have been processed.

By default, the maximum value is 1000. If you would like to change this setting, configure the following:

• Set intValue for CD_THROTTLE to the desired value.

CD_RDMGR_MAX_RETRIES

The maximum number of times a batch will be retried before rejection by the reading manager (rdmgr). This should rarely, if ever, be modified.

The default value is 10. If you would like to change this setting, configure the following:

• Set the intValue for CD_RDMGR_MAX_RETRIES to the desired value.

CD_GQ_SEARCH_THRESHOLD

The search for a valid GQ starts at the time of the meter data and starts searching backwards for a valid GQ.

If none are found, all the rows for that particular GQ are searched, causing a severe performance problem.

You can configure a cut-off point at which the search will be deemed complete in order to avoid this scenario. By default, the cut-off point is set to 40 days.

If this situation does not apply in your circumstance, set this to 2000 (~5 years).

If you would like to change the default value, edit the following:

• Set the intValue for CD_GQ_SEARCH_THRESHOLD to the desired value.

CD_METER_SEARCH_THRESHOLD

When calculating values for an accumulator meter, the search for the previous row starts at the time of the meter data and starts searching backwards for the previous row. If none are found, this searches all of the rows for that particular meter, causing a severe performance problem.

You can configure a cut-off point at which the search will be deemed complete in order to avoid this scenario. By default, the cut-off point is set to 40 days.

If this situation does not apply in your circumstance, set this to 2000 (~5 years).

If you wish to change the default value:

• Set the intValue for CD_METER_SEARCH_THRESHOLD to the desired value.

CD_MAX_MEAS2REALTIME_ITEMS

This provides the maximum number of effective object items returned by EFMxfer_getEffectiveItems. This is used by meas2RealTime in AVEVA Pipeline Operations for Gas.

By default, the maximum number of effective object items is set to 110.

If you wish to change the default value:

• Set the intValue for CD_MAX_MEAS2REALTIME_ITEMS to the desired value.