...
Ensure that any scheduled jobs on the deployment Advanced Options instance are disabled.
Avoid conducting the deployment process during business hours to prevent user interference.
Maintain a stable and fast internet connection throughout the deployment.
Monitor the firewall for potential performance limitations that could impede the deployment process.
Verify sufficient JVM resources and ensure adequate resource allocation, particularly JVM heap space. You can refer to the Jira Sizing guide: https://confluence.atlassian.com/jirakb/jira-server-sizing-guide-975033809.html and https://confluence.atlassian.com/enterprise/data-center-performance-946040735.html.
Install the most recent version of the Configuration Manager for the Advanced Options app on both the source and target instances to access the latest features and bug fixes.
When deploying a project with issues, avoid including attachment files in the snapshot to prevent unnecessary growthincreases in snapshot file size. Instead, copy the attachments for the exported projects and move them to the target system. For more information, refer to the link: Move Attachments.
Disable re-indexing in the advanced settings by default to prevent a non-locking reindex after the issues are imported, which is slow. If you disable it, the deployment will not start a reindex, and you will have to start one yourself after the deployment is done. However, you can start a locking reindex, which should be considerably faster. For more information, refer to the link: Advanced Options.
We kindly request you to schedule the deployment during off-business hours to enhance performance and reduce deployment time.
Additionally, for Data Center users, please refer to our Data Center recommendations page - https://appfire.atlassian.net/wiki/spaces/CMJ/pages/82778043/Data+Center
It is important to ensure that both the source and destination instances have sufficient resources allocated, especially JVM heap. You can consult the Jira Sizing guide at https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html
We recommend allocating double the recommended amount for the heap. Typically, 8-16 gigs of JVM heap are sufficient for large migrations and, in some cases, even 32G.
If you encounter performance issues with Jira Data Center during deployment, please refer to the following article for more details:
More information:
Also, kindly refer to the below Data Center KB articles for additional insights on performance issues.
Jira Data Center performance problems during deployment
Data Center
...