Customizing the Number of Measures To DeQueue

You can configure the process to pull pending items from the Queue table using the MaxMeasuresToDequeue settings in the EmiRuntimeConfigurator.xml file. This settings allows multi-processing of Measures waiting to be updated due to TDD changes. In order to take advantage of today's multi-processing architecture, Measures are processed using multiple threads. Each measure also uses multiple threads internally to handle simultaneous calculation processing so this process can, as well, initiate multiple threads.

Note: This configuration setting is only used for Measures that are related to Time Defining Dimensions.

Depending on your hardware and/or Model configuration, it might benefit you to modify this setting. This is an advanced setting which means that the default setting may not fit all scenarios.

For a machine that only processes the BI Gateway Runtime software, it would depend on the number of cores and the complexity of your model; specifically how many measures you have, how many calculations per measure, and the refresh rate of your measures.

The following scenarios that might indicate a required change to this setting:

• Configured number too low: Your Data Store's Model.Queue table should have few rows because it clears out rows that have been processed. If you notice that it is accumulating many rows, you may try increasing the number of the setting, given you have multiple measures in your model.

• Configured number too high: If you've changed the setting and notice that your Data Store's Model.Queue table has few rows but your CPU is running close to 100% over a long period of time, you may try to reduce the number of this setting.

For example, let’s say that the MaxMeasuresToDequeue is set to 1. If you have 3 measure requests in the queue, and 0 (zero) measures are currently processing, then the BI Gateway Runtime will pull and initiate only one request and process the time defining dimension update for one measure.

On the other hand, if a measure is already being processed but has not finished, then no additional measures are processed until the first one has finished.

You can allow more measures to be processed simultaneously by increasing the value in the EMI Runtime configuration setting.

To configure the MaxMeasuresToDequeue value

1. Open the EMIRuntimeConfigurator.xml file in a notepad editor from the BI Gateway Installation Bin directory. For example: C:\Program Files (x86)\Wonderware\Intelligence\Bin.

2. Edit the XML file and update the following information, which is set to 1 by default:

   <MaxMeasuresToDequeue>1</MaxMeasuresToDequeue>

3. Save and close the file.

4. Restart the Intelligence Runtime service in order for the MaxMeasuresToDequeue setting to take effect after changing this setting in the EMIRuntimeConfigurator.xml file.