How to improve performance.

Introduction

To improve app performance, focus on more than just the hardware. Regularly maintain the app and review its settings. The best practices for maintaining app performance also prevent slowdowns in a self-hosted Jira environment due to data synchronization.

The recommendations on this page focus on four main areas:

• making data sync faster

• speeding up module loading

• improving UI responsiveness

• lower risks of Jira issue pages slowing down

Optimized and safe data synchronization

If you are experiencing Jira performance issues caused by BigPicture data sync, check the performance settings in App Configuration.

The performance settings help you optimize BigPicture syncs with Jira. This can significantly reduce the chances of a negative impact on Jira, even if over 30,000 users are working on over 1 million issues.

The following settings can also speed up the data sync.

Access the synchronization settings

A Jira admin can access the Performance tab in App Configuration:

1. At the top bar, go to Apps > BigPicture.

2. Go to App settings (wrench icon at top right) > Performance. You are taken to the Sync rules tab in the Performance section.

Open

Adjust the partial sync settings

Settings	Description

Settings	Description
Synchronization time interval Open	Adjust how often BigPicture syncs data (a range of 1-10 seconds). Increase the value to boost app performance (synchronization less frequent).
Updates processing control Open	Switch the processing mode to manage better the high volume of BigPicture updates in Jira and vice versa. Simple updates processing - One queue for processing all updates. The app should process all updates quickly, but when dealing with large volumes of data, it may be inefficient and cause a risk of high CPU load (if only one queue is used, it may run continuously without emptying). Optimized updates processing (recommended) - Splits a single long queue into into multiple smaller queues for more efficient management. Updates from Jira to frequently used boxes are the priority (high-priority queue). Updates from less used boxes go to the low-priority queue, which processes them every fifteen minutes. This prevents the app from dealing with excessive data loads at short intervals, reducing the risk of high CPU load and negative impact on Jira. Limited updates processing - This mode continuously updates the boxes you use the most, but there is no low-priority queue. While this mode reduces the risk of negative effects on Jira, syncing less frequently used boxes will take longer. We don't recommend using this mode if you work with large data volumes.
Box activity threshold Open	Defines which boxes are classified by the app as active. Enter a value ranging from 1 to 144 hours.
Active box limit Open	Limits the number of boxes supported by the high-priority queue. Enter a value ranging from 10 - 100 boxes.
Box synchronization threshold Open	Lets you set a synchronization timeout. Enter a value ranging from 5 - 10,000 milliseconds.

Schedule full synchronization

Scheduled sync ensures data in all boxes is up to date. Schedule the sync using a cron expression.

We recommend scheduling a sync once a week during the off-peak hours. When the sync is running, performance might decrease.

Open

Adjust live sync settings

Live sync eliminates the need to refresh a page to see the changes made by other BigPicture and Jira users. The sync interval, which is expressed in seconds, determines how frequently data from individual modules and markers is synchronized.

To improve performance:

• Increase the sync interval (less frequent syncs) OR

• Use the toggle switch to disable live sync.

Go to: Switch to the Live sync tab to make adjustments.

Open

Evaluate custom field mapping

Use custom field mapping only if you need it.

Field mapping is responsible for bidirectional data synchronization between BigPicture and Jira.

Clean up the box structure

As the project portfolio in your organization grows, so does the number of boxes in the box hierarchy.

• Close and archive boxes that are no longer needed - BigPicture doesn't refresh closed and archived boxes, which results in better app performance.

• Delete unnecessary boxes (e.g., it's just a test box).

You may also want to clean up old and unused Jira projects.

• Archive old Jira projects

  • cloud Archive a space | Atlassian Support

  • data center Archiving a project | Administering Jira applications Data Center 11.1 | Atlassian Documentation

Faster module page load time

When working with the app, you might notice that a module page doesn't load fast enough. The following changes speed up data sync.

Customize task-related performance settings

The Performance tab includes additional settings worth considering to enhance page load time while using BigPicture modules.

Settings	Description

Settings	Description
Maximum tasks to load Open	To enhance loading speed, limit the number of tasks simultaneously displayed by BigPicture. A lower limit will result in improved loading performance.
Task grouping limit Open	Limit the maximum number of tasks the app can group to optimize the process. By reducing the number of tasks, the app can perform grouping faster.