JIRA Service desk is slow

[GG]

Hi,

JIRA Service desk is very slowly. we did everything that was suggested. Now we know that JIRA’s configuration lead to software slowdown. our test result show that JIRA is acceptable without configuration. What to do to fix this problem?

Regards

[Nic Brough -Adaptavist-]

Don't configure it to be slow?

I'm afraid we can't tell you anything, you've not explained what you are doing to make it slow, or why, so we can't give you more than "don't do it that way"

[Suhas P]

What do you mean everything that is suggested?

If it is freshly installed Jira then try increasing JVM heap memory in sertenv.sh (for unix based servers).

[Nic Brough -Adaptavist-]

Be careful about that, don't just sling a huge amount at a memory increase, do it in small steps, adding maybe 256M at a time, rather than 4Gb.  Large increases can just change the profile of the problem, rather than show you can solve it with increases. 

A classic example from my past was "Jira is slow, seems to go through slow patches for 5 minutes maybe once or twice an hour".  Doubled the heap space, and it got worse - slow patches for 20 minutes once an hour, with phases of "completely unresponsive"

[GG]

Thanks for your reply. We adjusted JVM heap memory, DataBase, Tomcat,...

Each transaction in the workflow takes more than 20 seconds. We provided test environment, our test result show that JIRA is acceptable in physical server and DB, without configuration. What to do to fix this problem?

[Nic Brough -Adaptavist-]

We don't know, you have not told us what you have, what you have configured or what is actually slow.  Take a look at the configuration of a "slow" transaction - what actually is slow?  Page load as it refreshes?  Or the actual transition processing?  What processes are running during the transition?  What are the validators and post-functions?

[Suhas P]

@GG What is physical location of the application and database servers? Are they located in the same data centre ? If database and application servers might have latency. Try relocating servers or install database on the same server as application and check the response time and speed.

[GG]

After various tests, we found that the problem was from JIRA Service Desk automation rules. Without automation rules(about 400 different rules) , the speed of JIRA workflow's actions is about three times better. We need rules for automation. we have merged some rules. What should we do to optimize the rules?

[Nic Brough -Adaptavist-]

Remove as many as possible.  400 automation rules running in one service desk implies you've massively overcomplexified a process and then tried to patch over that mistake by automating it to death.

Go back to the process and fix that, you should find it will bring automations down to a sensible level, which means your system will then perform properly.  As a rule, I start to question a process that "needs" more than 10, and really worry when you hit 25.