Knowledge Base

 View Only

Optimizing Jama Connect's Performance Using the System Health Report

By Eric Rickson posted 02-07-2017 21:38


Red, yellow, exclamation points... What's the deal?

You haven't done anything wrong
The System Health Report is highlighting areas in Jama Software where your particular configuration can be optimized to improve the user experience. For example, the "% Recommended" thresholds indicate where users might experience suboptimal performance. We say “might” because these figures are based on our own stress tests, but you may not experience any problems.

Every system is a little different. Beyond the factors shown in the health report, the experience depends on many additional factors including hardware and network speed. Find more information below about how to optimize your specific system’s performance in each major area.

If, on your report, you have crossed the recommended threshold for projects, there are a few things you can do.
  • Move items into a separate project and continue work on them.
  • Move inactive items to an archive project.
    • Note: The Jama Software system employs soft deletes by default, meaning they are still in the database should data need to be recovered. If you have recently deleted may items, they may still be counted in the total item count for that project. If that is the case, action may not be required to make your project smaller -- deleted items are not actively indexed or displayed, so performance may be fine.

  • The Explorer Tree is configured to display a default of 250 items to ensure best performance. This can be configured to display more items, but keep in mind it may impact performance.

Larger reviews take a longer time to load, and are harder for users to read through. Consider breaking up large reviews so users can more easily participate. Here are a few ways we recommend dividing reviews:
  • By role or expertise. Create reviews containing only the items you want a particular group to read.
  • By timeframe. Split up content into reviews by milestone dates. If you're Agile, for example, this may mean only reviewing epics and stories planned for the next sprint.
  • By document section. To keep team members focused, split up documents by sections or topics. It may make naming the review easier as well.
  • Limit Jama item fields to well under 10,000 characters (2000 words). Items with excessively large fields will be skipped in Review Center's Compare View and you will see this notice: 

    compare versions error, if fields contain too many characters


Reports can vary drastically in size and complexity depending on how they are designed. Before running a report it is not always clear how long it will take to gather the requested information. Rather than attempt to calculate it up front, the Jama Software System Health Report captures how long reports took to run over a certain threshold. If you see reports that are especially long running, there are a few options.
  • Reduce the size of the report if possible. For help contact your account representatives.
  • Kick off the report run during off hours. It'll run faster, and it won't be competing for server resources with users.

Keep the Test Center running efficiently by following these tips:
  • Keep the number of test cases in a test run to 4,000 or fewer. This ensures that when a test cycle is generated, it runs smoothly.


Jama was optimized to perform assuming certain hardware. Please review the Jama Software User Guide for more information.

  • There is a thorough article worth reading if you are using Jama in an enterprise-sized environment.
  • If you have an on premises installation of Jama Software, admins can access previously run reports created in the last 7 days in the "Report Temp" folder. Previously run reports can then be analyzed for opportunities to increase efficiency.
  • See this article about optimizing Reuse.