If your Jira Server instance is already on the verge of its endurance, you might be thinking that the possibilities of vertical scaling are no longer available. You might invest in the improvement of the hardware parameters, but you’re probably asking yourself what else is there to do. Here’s the answer.
Reduce the number of Jira Server users
The primary factor influencing the efficiency of your instance is the number of users and their way of interacting with the application, which, along with their increase, becomes more burdensome.
Unfortunately, the solution to this problem is not as simple as it seems. We cannot tell employees to use the application less frequently. We also cannot remove system users. However, we can divide them.
Separating one instance of Jira can be a solution that not only affects performance but also increases data security. Thanks to this, we can make it so that, for example, HR and accounting processes are handled in a dedicated instance.
Spread the load evenly over two instances
Another factor affecting the performance of Jira Server is a large number of add-ons, their type, and how they’re. For example, an application that loads data from an external system on its every page or processes information from dozens of related applications will cause the screen to load longer.
The division of the Jira instance is also the solution to this problem. An enterprise where many teams have different needs, it’s often difficult to give an extension up. Thanks to the separation of the instance, we can distribute the load evenly between teams performing various tasks in the company processes. Installing a new Jira instance with add-ons, such as Gantt charts or planning projects like Portfolio will release even more hardware resources and maybe also allow you to save on more expensive extension licenses.
How IssueSYNC helps to improve performance
Despite its advantages, this solution brings forth problems. One of them is the additional license costs for the second Jira instance or hardware resources. However, from a broader perspective, it may turn out to be a good investment. Another challenge may be difficult communication and data flow between teams. However, it is also a problem organizations can solve. Thanks to the IssueSYNC application available on the Atlassian Marketplace, we can synchronize two Jira instances with each other. We gain a trouble-free and automatic synchronization of applications, attachments, or comments. Our team doesn’t have to worry that some information did not reach it.
Jira Data Center – an alternative solution
If you can’t implement the solution we propose at your organization for various reasons, there’s yet another option: transition to the Jira Data Center. This type of distribution allows companies to scale Jira horizontally, that is, create any number of instances with the same configuration and data. You can read about its performance benefits on the Atlassian website.
However, note that it will be a much more expensive solution than having one Jira Server due to the usually higher pricing of extensions.
Solution Architect for Atlassian Jira platform with a holistic approach. He combines strong technical skills with a business-oriented perspective providing a bridge between technical and non-technical stakeholders. Currently, focusing on application integration. Together with a team of experts, he helps companies to design, implement and tune Atlassian products.