Jama Connect User Guide

Resource sizing for servers

For optimal performance, we recommend that you estimate the needs of your environment's servers before installing Jama Connect.

Use the following tables to determine resources for your application server and database server. Monitor usage and adjust your settings as necessary.

If you're approaching the Enterprise threshold, contact support for customized recommendations and advanced, multi-server setup.

Application server

Small

Medium

Large

Enterprise

Active items in system

Up to 600,000

Up to 2 million

2–4 million

4 million+

Active projects

Up to 100

Up to 500

Up to 1,000

1,000+

Concurrent users

50 or fewer

Up to 500

Up to 1,000

1,000+

CPU cores

4

8

16

Contact Support

Total system RAM

16 GB

24 GB

32 GB

Contact Support

Database server

Small

Medium

Large

Enterprise

Active items in system

Up to 600,000

Up to 2 million

2–4 million

4 million+

Active projects

Up to 100

Up to 500

Up to 1,000

1,000+

Concurrent users

50 or fewer

Up to 500

Up to 1,000

1,000+

CPU cores

4

8

16

Contact Support

Total system RAM

16 GB

32 GB

64 GB

Contact Support

Total system RAM can vary if you're using memory intensive workflows such as reuse, exporting, move items, integrations, and batch updates.Database sizing is based on your usage patterns and platform. You must have a minimum of 4–8 cores and 16–24 GB of memory. Consult with your database administrator when determining database size.

The memory allocation allows for minimum headroom. If you need to run additional software for monitoring and analysis, consider the additional system requirements for that software. Configure dynamic memory settings as needed in the Admin Console. 

We recommend setting up dedicated volumes for the data your application is going to write. For information about setting up these volumes, see Preparing your application server, Example: Setting up dedicated volumes.

The storage calculator can help you determine your particular needs for the application server.

Item

Default location

Recommended file system type

Explanation

Small example

Enterprise example

Calculate your own

Operating system

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 attachments you're storing

40-100 GB

100 GB

______ GB

Replicated

/var/lib/replicated/

EXT4

Tip: Configure snapshots to be stored in /data/replicated/snapshots/ to ensure backup

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.