Resource allocation on the next-generation platform
You can add servers when resources are available. However, if you are not able to start more
servers because many servers are running simultaneously, perform one of the following tasks to
release the resources.
- Stop the servers that are not needed or unused.
- Stop any failed servers as they use resources.
- Schedule the process such that the servers use the CPU and memory resources optimally.
- To maximize the number of server instances on development and test environments, for agent and integration servers that are created or modified, the performance profile is automatically set to Balanced. The other profiles are reserved for the preproduction and production environments to support high-volume use cases. Modifications to the existing servers are automatically updated to the Balanced profile.
Server status and its effect on resource allocation
The resource allocation is affected based on the status of the servers, as explained in the
following table:
| Server status | Resources used |
|---|---|
| Not started | No |
| Started | Yes |
| Running | Yes |
| Failed | Yes |
Resource allocation based on performance profile
The resource allocation is based on entitlements such as order lines per hour, Sterling Call Center users, store devices and more as specified in your contract or service description. For more information, see the service description.
For production environments, all accounts start at a minimum of 60 server instance, which can be distributed among the server profiles. For example, 60 server instances might translate to 42 balanced, 12 memory, and 6 computer server instances.