Last Updated on
Topic: How Ephesoft license service allocates cores in Transact
Applicable Ephesoft versions: All
This article explains how the Ephesoft license service allocates cores in a Transact system.
Ephesoft Transact on a standalone installation
In this case, the license service will check how many cores the installed license is for and will take that exact number, provided that the machine has enough cores. Normally, this means that if you have an 8-core machine you will also have an 8-core license and so the license service will use the 8 cores.
Alternatively, the user might want to use less cores than the total available. This is indeed possible by obtaining a license for less cores than the total -e.g. installing a 4-core license on an 8-core machine. In this case Transact will run using only 4 cores of the total of 8 available.
Note: Running Transact with less cores than those available in the machine is only possible on a standalone install.
Ephesoft Transact on a clustered environment
This case is a bit trickier. When the license server starts it will take all the cores from that first server and subtract it from the total available cores in the license. It will do this recursively with every new node added to the cluster until it runs out of available cores.
Note: The minimum number of cores taken per node will be 4. Thus, if you have a server with 2 cores, the license service will still subtract 4 from its total.
For the sake of clarity, these are some examples:
- 8 core license, you have 2×4-core servers: (License completely used)
- 10 core license, you have 2×4-core servers: (License underutilized)
- 4 core license, you have 2×2-core servers: (First server takes 4 cores, second gives a license error)
- 10 core license, you have 2×8-core servers: (First server takes 8 cores, second attempts to get the minimum 4 but gives a license error)