Skip to main content

Jama Connect User Guide

Application server requirements and resource sizing

To install and run Jama Connect successfully, your application server must meet these requirements.

Requirement

Notes

Be a dedicated application server

Make sure that Jama Connect is the only application running on the application server. External services can affect the stability of the application, for example by consuming memory resources.

Have sufficient storage, CPU, and memory

Performance depends on the amount of CPU and memory provided.

Estimate the appropriate size and resources for your application server:

  • Traditional installation — See Traditional installation – Resource sizing for application server below

  • KOTS installation — See KOTS installation – Resource sizing for application server below

Have administrative rights to that server

An admin must have proper permissions to maintain the application, perform upgrades, and access the server for regular maintenance.

Use compatible software and environments

Verify that you're using supported software and environments compatible with the most recent self-hosted release.

Traditional installation — Resource sizing for application server

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

The following table can help determine needed resources for your application server. Once you're up and running, you can monitor usage and adjust settings as needed from the Config tab in the KOTS Admin Console.

Application server

Small

Medium

Large

Enterprise

Active items in system

600,000

2 million

2–4 million

4 million+

Active projects

100

500

1,000

1,000+

Concurrent users

50

500

1,000

1,000+

CPU cores

4

8

16

Contact Support

Total system RAM

16 GB

24 GB

32 GB

Contact Support

If your usage approaches the Enterprise threshold, contact Support for customized recommendations and advanced, multi-server setup.

Use this storage calculator to determine what you need for your application server.

Item

Default location

Recommended file system type

Explanation

Small example

Enterprise example

Calculate your own

Operating systems

N/A

N/A

Not included in this calculation

N/A

N/A

______ GB

Docker images

/var/lib/docker

XFS with ftype=1, or EXT4

Variable

30 GB

50 GB

______ GB

User data

/data

NFS

Filesystem can vary, but consider size of stored attachments

40–100 GB

100 GB

______ GB

Replicated

/var/lib/replicated/

EXT4

Configure snapshots to be stored in /data/replicated/snapshots/

20 GB

30 GB

______ GB

Log files

/logs

EXT4

10 GB (fixed)

10 GB

10 GB

10 GB

Total:

100 + GB

160 + GB

______ GB

Important considerations

  • To avoid performance issues, use XFS with the dtype option of ftype=1 or use EXT4. For Docker's default data root directory, /var/lib/docker, if an XFS filesystem doesn’t have the dtype attribute set to ftype=1, performance can degrade for container creation at startup.

  • Jama Software supports internally hosted network storage mounts (NFS). EBS is suggested in cloud-based environments. Cloud NFS (like EFS) isn't supported because Docker doesn't work with EFS.

KOTS installation — Resource sizing for application server

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

Recommended operating system

Storage space

Ubuntu 18.04 or Ubuntu 20.04

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.

Recommended — Every node has the same storage space.

Note

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

The following tables can help determine resources for the primary node of your application server. Once you're up and running, you can monitor usage and adjust settings as needed from the Config tab in the KOTS Admin Console.

Important

Horizontal scaling used with minimum requirements can cause performance issues. Best to use the recommended requirements to avoid performance issues.

Table 2. 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



Table 3. 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



The following table can help determine resources for the secondary node of your application server. Once you're up and running, you can monitor usage and adjust settings as needed from the Config tab in the KOTS Admin Console.

Table 4. 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