Introduction:
In a Private Cloud setup, the number of concurrent core for each worker can be configured via the InTime Server.
More Information:
The command .global.set.maxrun has been deprecated for InTime Server built after 14 July 2015. It has been replaced by .global.set.concore.
In Private Cloud Console, execute the following commands. It will take 2 heartbeats (maximum duration of 4 minutes) to propagate the new concurrent core value to the InTime Agents (provided that an Agent’s status is FREE).
user> .admin
admin> .global.set.concore=4
Proceed to set concurrent core? ('y' for Yes or 'n' for No) [y]
admin.confirm> y
admin> .global.setting
+---------------------------------+--------------------------------------------+
| SETTING | VALUE |
+---------------------------------+--------------------------------------------+
| File transfer port | 39941 |
| Admin console port | 39942 |
| File transfer method | SFTP |
| Server working directory | /home/intime/intimeserver/./plunify_server |
| Working Directory | $USER_HOME/plunify/worker_jobs |
| Concurrent core for each worker | 4 |
| Log verbosity | normal |
| Timestamp | 2014-10-03T06:06:15 |
+---------------------------------+--------------------------------------------+
admin> .cpu
+-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+
| NO. | CLIENTID | JOBID | USERID | STATUS | ALIVE | TYPE | PHYCORE | CONCORE | MAXCORE |
+-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+
| 1 | user10_00505621E3EE | | user10 | FREE | YES | INTEL 2.7 | 4 | 4 | 0 |
+-----+---------------------+-------+--------+--------+-------+-----------+---------+---------+---------+
Applies to:
- Linux Operating System
- Windows Operating System
Knowledge Base ID: 6009 - Last Review: May 21, 2014 - Revision: 1.0