Jama Connect® Enterprise Scalability & Performance

Preston Mitchell
Preston Mitchell
  • Updated
Audience: Everyone

Products and Versions Covered: 

  • Cloud/CVC
  • Self-hosted, Replicated - KOTS
  • Jama Connect version 9.32 and later

Summary

Jama Connect® is a platform used at scale across many scenarios. The platform is designed to allow teams to scale to very large numbers while providing safeguards to prevent rogue users or batch operations from negatively impacting performance for other users.

Resolution

Scale

The amount of content a system can handle is primarily measured by data volume. As organizations scale, requirements management software must support parallel development, standardized processes, and cross-program visibility, which can lead to a large number of programs and companies. As of release 9.32, Jama Connect's scalability benchmarks are: 

  • Items per project – 10 million
  • Items per instance – 100 million
  • Concurrent users – 10,000

Performance

Performance is how well the system handles work at the current data volume. It is primarily measured by speed and responsiveness. In our scalability benchmarks above, Jama Connect maintains industry-leading performance. We gauge our cloud environment's performance at consumer web scale, which is superior to most enterprise B2B applications.

P75 refers to the 75th percentile of page load times for a website, a key performance metric that indicates 75% of user sessions experience a page load time equal to or faster than a specific value. For Jama Connect:

  • The P75 total page load time (from request to full browser paint) averages 3.41 seconds.
    The cumulative average across all page loads is under 3 seconds (2.66). 

Please refer to this article in the references for details on the application performance of Jama Connect.

Safeguards

To maintain performance at scale, Jama Software uses safeguards to ensure that rogue users or batch operations do not negatively impact the userall users. These safeguards are defined in our help guide for each batch operation. Examples of safeguards: 

  • Batch delete or update is limited to 5,000 items per batch. Jama will slowly update objects in the background to facilitate consistent performance.
  • Up to 25 million API calls per month. Concurrent API calls are throttled to protect performance. If exceeded, a 429 response is sent to the script/integration to signal throttle limit, preserving performance for all users.
    • Scripts and integrations should be designed to handle a 429 response by implementing exponential backoff: e.g., wait 3 seconds, then retry. If still throttled, wait 5, then 8, then 13, and so on.
    • Large data pulls from Jama are better done in an offline ETL system like Jama Connect DataTap™, which provides a daily copy of your Jama database for business intelligence reporting. This preserves API performance for actual write operations, such as automations and integrations. 

IMPORTANT: Access to the REST API is limited to users with a Named Creator Jama Connect license, including endpoints in v1, labs, and SCIM. Users without a Named Creator Jama Connect license, including those with a Creator Float License, do not have access.

Additional Resources:

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.

 

Was this article helpful?

2 out of 2 found this helpful

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.