serverProfiles parameter

Use server profiles to define common configurations for CPU and memory requirements that can be applied to a set of Sterling™ Order Management System Software workloads like appserver, agent or integration servers, and more.

Note: Server profiles are designed to specify pod request and limit resources in a Kubernetes environment, and are not meant for setting the JVM arguments such as Xmx and Xms. Tailor the Xms and Xmx settings according to your specific use cases.

Workloads that require a specific set of CPU and memory resources can be grouped under a single profile. With Server profiles you can manage resource requirements for a set of workloads in a common location.

serverProfiles are used to define list of server profile definition. Each profile can define its own request and limit values of CPU and memory. Servers can refer these profiles by just using profile name.

Default profiles

By default, the following three server profiles are available:

balanced
balanced profile can be used for typical Sterling Order Management System Software workloads that has small to moderate use of CPU and Memory resources. Following is the resource requests and limits for balanced profile.
```
requests:
  memory: "1Gi"
  cpu: "100m"
limits:
  memory: "1.5Gi"
  cpu: "1000m"
```
memory
memory profile can be used for workloads that need more memory for processing. Following is the resource requests and limits for memory profile.
```
requests:
  memory: "1.5Gi"
  cpu: "100m"
limits:
  memory: "4.5Gi"
  cpu: "2000m"
```
compute
compute profile can be used for workloads that need more CPU cycles for processing. Following is the resource requests and limits for compute profile.
```
requests:
  memory: "1Gi"
  cpu: "1000m"
limits:
  memory: "2.5Gi"
  cpu: "4000m"
```

You can also define the custom server profiles, if the default profiles do not suit your requirements.

Profiles for different workloads

Use the following profiles based on the intensity of your CPU and memory workload. These profiles simplify your sizing requirements by providing predefined memory and CPU requests and limits.

small

requests:
  memory: "512Mi" 
  cpu: "200m" 
limits:
  memory: "1Gi"
  cpu: "1000m"

medium

requests:
  memory: "1Gi"
  cpu: "500m"
limits:
  memory: "2Gi"
  cpu: "2000m"

large

requests:
  memory: "2Gi"
  cpu: "500m"
limits:
  memory: "4Gi"
  cpu: "4000m"

huge

requests:
  memory: "4Gi"
  cpu: "500m"
limits:
  memory: "8Gi"
  cpu: "4000m"

massive

requests:
  memory: "4Gi"
  cpu: "1000m"
limits:
  memory: "16Gi"
  cpu: "8000m"

The following YAML snippet is a sample schema of the serverProfiles for defining custom server profiles:


  serverProfiles:
  - name: ""
    resources:
      limits:
        cpu: 
        memory: 
      requests:
        cpu: 
        memory:

The following table explains the attributes applicable for the serverProfiles parameter of OMEnvironment.

Table 1. Properties for `serverProfiles`
Property	Default value	Value type	Required	Description
`name`		`string`	Yes	Specify the `serverProfile` name.
`resources`		`object`	Yes	Specify the CPU and memory resource requests and limits. For more information, see Resource Management for Pods and Containers.