Introduction:
PHYCORE, CONCORE, MAXCORE are values related to each InTime Agent, and can be shown using the Private Console’s .cpu command. Each Worker machine can have one or more InTime Agents running on it.
user> .cpu +-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+ | NO. | CLIENTID | JOBID | USERID | STATUS | ALIVE | TYPE | PHYCORE | CONCORE | MAXCORE | +-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+ | 1 | user10_00505621E3EE | | user10 | FREE | YES | INTEL 2.7 | 4 | 4 | 0 | +-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+
The Concurrent Runs is a user property visible in the InTime GUI’s Properties panel.
More Information:
PHYCORE (read-only) stands for “physical core”. It is the number of physical CPU cores that a Worker has. This value cannot be changed and is tied to the respective machine.
CONCORE (user-configurable) stands for “concurrent core”. It is the number of concurrent cores that a Worker can use at any one time. This value sets the maximum number of Worker processes that an agent can spawn. CONCORE cannot be greater than PHYCORE. To set CONCORE, use .global.set.concore in Admin mode using the Private Cloud console. CONCORE is the number to change if your Worker machines are too overloaded or too lightly-utilized.
MAXCORE (user read-only, set by InTime Server) stands for “maximum assigned core”. It is the number of cores that a Worker is currently using when working on a job. MAXCORE cannot be greater than CONCORE. This value is assigned by the InTime Server. In other words, if a Worker’s MAXCORE is 2, that means the Agent has spawned two Worker processes to work on two revisions.
Concurrent Runs (user-configurable) is a property that can be set by the user in InTime. This value limits the number of concurrent compilations for a particular job. For example if a user sets Concurrent Runs to 10, this means that the maximum number of Worker processes spawned is capped at 10.
Scenario #1
- Number of Agents running: 6
- There are nine revisions to compile.
- The user sets Concurrent Runs to 9.
- The admin user sets CONCORE to 2.
- InTime Server’s priority: CORE
Outcome: Setting priority to CORE tells the Server to use all the available concurrent cores in each Agent before proceeding to the next Agent. The last agent will not be assigned any revision to run.
user> .server.properties +-----+------------+---------------+-------+ | NO. | READ/WRITE | KEY | VALUE | +-----+------------+---------------+-------+ | 25 | R/W | PRIORITY_FLAG | CORE | +-----+------------+---------------+-------+ user> .cpu +-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+ | NO. | CLIENTID | JOBID | USERID | STATUS | ALIVE | TYPE | PHYCORE | CONCORE | MAXCORE | +-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+ | 1 | user10_00124ED00AF1 | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 2 | | 2 | user10_0023FA093281 | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 2 | | 3 | user10_0034FD0911A2 | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 2 | | 4 | user10_0040128348EF | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 2 | | 5 | user10_00505621E3EE | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 1 | | 6 | user10_00889013FB11 | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 0 | +-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+
Scenario #2
Given the same scenario, but this time, with a Server priority set to WORKER, the InTime Server will assign at least one revision to every Agent in round-robin fashion.
Outcome: The last three agents will only be assigned one revision each.
user> .server.properties +-----+------------+---------------+--------+ | NO. | READ/WRITE | KEY | VALUE | +-----+------------+---------------+--------+ | 25 | R/W | PRIORITY_FLAG | WORKER | +-----+------------+---------------+--------+ user> .cpu +-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+ | NO. | CLIENTID | JOBID | USERID | STATUS | ALIVE | TYPE | PHYCORE | CONCORE | MAXCORE | +-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+ | 1 | user10_00124ED00AF1 | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 2 | | 2 | user10_0023FA093281 | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 2 | | 3 | user10_0034FD0911A2 | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 2 | | 4 | user10_0040128348EF | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 1 | | 5 | user10_00505621E3EE | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 1 | | 6 | user10_00889013FB11 | 8 | user10 | BUSY | YES | INTEL 2.7 | 4 | 2 | 1 | +-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+
Applies to:
- Linux Operating System
- Windows Operating System
Knowledge Base ID: 7000 - Last Review: Jul 14, 2015 - Revision: 1.0