...
Make sure to disable any scheduled jobs on the deployment Jira instance.
Avoid the deployment process during business hours, as users might access the application and perform some other operations.
Make sure to have a stable and fast internet connection during the deployment.
Please check/monitor the firewall if it is causing any performance limitations which may slow the deployment process.
Make sure to have sufficient JVM resources, and please make sure that you have enough resources allocated to your instances, such as JVM heap space in particular. 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.htmlIt is advisable to ensure that the most recent version of the Configuration Manager for the Jira app is installed on both the source and target instances. This will guarantee access to the latest features and bug fixes.
In case of deploying a Project with issues, Including attachment files can make the snapshot grow very large, which is why do not include attachment files in the snapshot. Copy the attachments for the exported projects and move them to the target system. During the deployment with Configuration Manager, you will be presented with an option to provide the path where the files reside on the target system. This will keep the snapshot small and speed up the deployment. For more info, refer to the link: Move Attachments
Disable the re-indexing in the advanced settings - Advanced Options
By default, CMJ will start 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.
Also, we request you to run the deployment during off-business hours which improves the performance and deployment time.
Additionally, please refer to our Data Center recommendations page(Applicable if you are in Datacenter) - https://appfire.atlassian.net/wiki/spaces/CMJ/pages/82778043/Data+Center
Ensure that source and destination instances have sufficient resources allocated - JVM heap in particular - you can consult with Jira Sizing guide https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html
We recommend double the recommended amount for the heap. Usually, 8-16 gigs of JVM heap are enough for massive migrations - even 32G.
For Jira Data Center performance problems during deployment, please follow this article for more details.
More information:
Also, please refer to the below data center KB articles for more details on performance issues.
Jira Data Center performance problems during deployment
Data Center