Skip to main content
Version: 10.2
warning

This page is intentionally hidden from navigation but remains accessible via direct link. It is retained for internal reference purposes only and may contain outdated or transitional content.

LoadManager

The loadmanager (openit_loadmanager) is an application that manages the sequence of the data processing jobs. The processes could be pending, queued, running, finished, blocked, or garbage.

Loadmanager runs in the background of the Open iT server by default, following its recommended behavior. But if needed, you can configure and run it manually with the following instructions.

danger

You need support's assistance to do this. Please coordinate with them to make sure everything goes smoothly.

Requirements​

  • Open iT Core Server
  • Administrative Rights

Configuring the Loadmanager​

To configure how much CPU usage the loadmanager can utilize, follow these steps:

  1. Go to the Components directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\Components, and open loadmanager.xml.

  2. Configure the maximum available cores you want the loadmanager to utilize. a. Locate object node max-cores under object node loadmanager and set its value to the maximum available cores you want the loadmanager to utilize.

    loadmanager.xml
    <Object>
    	<Name>max-cores</Name>
    	<Description>Maximum available cores the LoadManager can utilize. (Zero means utilize all available cores.)</Description>
    	<Value type="Integer">0</Value>
    note

    Zero (0) means the loadmanager will utilize all available cores. This number can be the actual number of cores or higher if hyper-threading is active in the CPU.

    b. Locate object node limitation under loadmanager.max-cores and set its value to tune loadmanager for a more optimal run.

    <div style={{"counter-reset": "line-count 44"}}>
    ```xml {4} title="loadmanager.xml" showLineNumbers
    <Object>
    	<Name>limitation</Name>
    	<Description>For when max-cores is set to zero. If the value is a negative integer, reduce max value by at most this number of cores. (Will not reduce down to zero!) If the value is an integer followed by '%', then utilize this percentage of the total available cores.</Description>
    <Value type="String">80%</Value>
    ```
    </div>

    :::info[note]
    Specifying a negative integer will subtract from the total number of available cores, while a percentage value will do a relative subtraction.
    :::

  3. Configure the maximum available cores you want the queued heavy jobs to utilize.

    NOTE

    Processing of the following data types are considered heavy jobs:

    a. Locate object node max-cores under object node queue_heavy and set its value:

    loadmanager.xml
    	<Object>
    		<Name>max-cores</Name>
    		<Description>The maximum cores this queue can utilize. (A value of zero means the generic max-cores will be used.)</Description>
    		<Value type="Integer">0</Value>
    NOTE

    Zero (0) means the maximum defined by the overall setting, (e.g., If max-cores=0 and limitation=80% on a 20 core machine, there will be 16 cores available for the queued jobs).

    b. Locate object node limitation under queue_heavy.max-cores and set its value:

    loadmanager.xml
    	<Object>
    		<Name>limitation</Name>
    		<Description>For when max-cores is set to zero. If the value is a negative integer, reduce max value by at most this number of cores. (Will not reduce down to zero!) If the value is an integer followed by '%', then utilize this percentage of the total available cores.</Description>
    		<Value type="String">30%</Value>
    NOTE

    Specifying a negative integer will subtract from the total number of available cores, while a percentage value will do a relative subtraction.

  4. Configure the maximum available cores you want the queued normal jobs to utilize.

    a. Locate object node max-cores under object node queue_normal and set its value:

    loadmanager.xml
    	<Object>
    		<Name>max-cores</Name>
    		<Description>The maximum cores this queue can utilize. (A value of zero means the generic max-cores will be used.)</Description>
    		<Value type="Integer">0</Value>
    NOTE

    Zero (0) means the maximum defined by the overall setting, (e.g., If max-cores=0 and limitation=80% on a 20 core machine, there will be 16 cores available for the queued jobs).

    b. Locate object node limitation under queue_normal.max-cores and set its value:

    loadmanager.xml
    	<Object>
    		<Name>limitation</Name>
    		<Description>For when max-cores is set to zero. If the value is a negative integer, reduce max value by at most this number of cores. (Will not reduce down to zero!) If the value is an integer followed by '%', then utilize this percentage of the total available cores.</Description>
    		<Value type="String">100%</Value>
    NOTE

    Specifying a negative integer will subtract from the total number of available cores, while a percentage value will do a relative subtraction.

  5. Save the file.

  6. Open a command prompt with Administrator level privileges.

  7. Go to the bin directory:

    Example
    cd C:\Program Files\OpeniT\Core\bin

  8. Update the configuration file:

    Command Syntax
    openit_confbuilder --server

Running the Loadmanager​

  1. Open a command prompt with Administrator level privileges.

  2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Example
    cd C:\Program Files\OpeniT\Core\bin

  3. Run the command:

    Command Syntax
    openit_loadmanager <parameter 1> <parameter 2>...<parameter n>

    Optional Parameters

    NameDescription
    --helpUse this parameter to display the help text.
    --versionUse this parameter to display the application version information.
    --debug <arg>Use this parameter to specify the debug level.
    Possible values are:
    • 1 - info
    • 2 - debug
    • 3 - warning
    • 4 - verbose
    • 5 - trace
    -c <arg>Use this parameter to specify the path of the configuration file to use instead of the default.
    --pend <arg>Use this parameter to specify the base directory name of the pending jobs.
    --que <arg>Use this parameter to specify the base directory name of the queued jobs.
    --run <arg>Use this parameter to specify the base directory name of the running jobs.
    --fin <arg>Use this parameter to specify the base directory name of the finished jobs.
    --block <arg>Use this parameter to specify the base directory name of the blocked jobs.
    --garbage <arg>Use this parameter to specify the base directory name of the garbage job files.
    --maxcores <arg>Use this parameter to specify the maximum number of cores to be used.
    --allow-dependenciesUse this parameter for loadmanager to allow job dependencies.
    Optional Parameters for Running LoadManager