This article explains the best practices to overcome performance issues during a deployment using the Configuration Manager for Jira (CMJ) app.
\uD83D\uDCD8 Instructions
...
to follow while deploying massive data changes
...
Ensure that any scheduled jobs on the deployment Jira Advanced Options instance are disabled.
Avoid conducting the deployment process during business hours , as users might access the application and perform some other operations.Make sure to have to prevent user interference.
Maintain a stable and fast internet connection during throughout the deployment.
Please check/monitor the firewall if it is causing any performance limitations which may slow the deployment process.
Make sure to have Verify sufficient JVM resources , and please make sure that you have enough resources allocated to your instances, such as and ensure adequate resource allocation, particularly 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 .Install the most recent version of the Configuration Manager for the Jira Advanced Options app is installed on both the source and target instances . This will guarantee to access to the latest features and bug fixes.
In case of When deploying a Project 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 avoid including attachment files in the snapshot to prevent unnecessary snapshot size increases. Instead, 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 infoinformation, refer to the link: Move Attachments.
Disable the re-indexing in the advanced settings - Advanced Options By default, CMJ will start by default to prevent a non-locking reindex after importing the issues are imported, which is slow. If you disable it, the deployment will not start a reindex, and you will have to can start one yourself after the deployment is done. However, you can may also start a locking reindex after deployment, 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 For more information, refer to the link: Advanced Options.
Allocate double the recommended amount for the heap. UsuallyTypically, 8-16 gigs GB of JVM heap are enough is sufficient for massive migrations - even 32G.For large migrations and, in some cases, even 32 GB.
If you encounter performance issues with Jira Data Center performance problems during deployment, please follow this article refer to the following articles for more details
\uD83D\uDCCB Related articles
...