Skip to main content

Jama Connect User Guide

Resource sizing for application server (upgrading traditional to KOTS)

For optimal performance, estimate your application server needs before you install Jama Connect.

Requirements

  • Each node must have a minimum volume of 200 GB. Increase this size based on the size of the assets that you plan to save in Jama Connect. We recommend that every node has the same storage space.

  • KOTS must be up and running before you configure the application settings in the KOTS Admin Console.

Important

To avoid performance issues, use the recommended requirements for horizontal scaling, rather than minimum requirements.

Use the following tables to help determine resources for the primary node of your application server.

Minimum size (AWS instance sizing = m5.2xlarge)

CPU

RAM

CPU + memory settings

CPU + memory setting with horizontal scaling jamacores

8

32 GB

N/A

jamacore application settings:

  • Maximum CPU: 1000m

  • Maximum memory: 2 G

  • Maximum memory per container: 3 G

  • Number of ingress nodes 2

Recommended size (AWS instance size = m5.4xlarge)

CPU

RAM

CPU + memory settings

CPU + memory setting with horizontal scaling jamacores

16

64 GB

Supports:

  • 1,250 users with a ramp-up time of 30 seconds

Supports:

  • 1,250 users with a ramp-up time of 10 seconds

  • 2,500 users with a ramp-up time of 30 seconds

jamacore application settings:

  • Maximum CPU: 12000m

  • Maximum memory: 48 G

  • Maximum memory for container: 60 G

jamacore application settings:

  • Maximum CPU: 3000m

  • Maximum memory: 12 G

  • Maximum memory for container: 15 G

  • Number of ingress nodes: 2

Elasticsearch settings:

  • Maximum CPU: 8000m

  • Maximum memory: 8 G

  • Maximum memory for container: 10 G

Elasticsearch settings:

  • Maximum CPU: 8000m

  • Maximum memory: 8 G

  • Maximum memory for container: 10 G

Diff Service settings:

  • Maximum memory: 2 G

Diff Service settings:

  • Maximum memory: 2 G

Use the following table to help determine resources for the secondary node of your application server.

Secondary nodes dedicated to Elasticsearch: Recommended size (AWS instance size = m5.2xlarge)

CPU

RAM

CPU + memory settings

8

32 GB

Supports:

  • 2,500 users with a ramp-up time of 10 seconds

Elasticsearch settings:

  • Maximum CPU: 8000m

  • Maximum memory: 8 G

  • Maximum memory for container: 10 G

Tip

Once you're up and running, you can monitor usage and adjust your settings as needed.

In this section: