This article explains the best practices to overcome the performance issues during the CMJ deployment using the Configuration Manager for Jira (CMJ) app.
\uD83D\uDCD8 Instructions
Generally, these are some of the recommendations we suggest while deploying massive data changes.
Make sure to disable 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 Monitor the firewall if it is causing any for potential performance limitations which may slow that could impede 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 the avoid including attachment files in the snapshot to prevent unnecessary growth. 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 infoFor more information, 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 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.
Also, we We kindly request you to run schedule the deployment during off-business hours which improves the to enhance performance and reduce deployment time.
Additionally, for Data Center users, 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 It is important to ensure that both the source and destination instances have sufficient resources allocated - , especially JVM heap in particular - you . You can consult with 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. UsuallyTypically, 8-16 gigs of JVM heap are enough sufficient for massive migrations - large migrations and, in some cases, even 32G.
For If you encounter performance issues with Jira Data Center performance problems during deployment, please follow this refer to the following article for more details.:
More information:
Also, please kindly refer to the below data center Data Center KB articles for more details additional insights on performance issues.
Jira Data Center performance problems during deployment
Data Center