I have Jira Server instance installed on t2 large AWS EC2 instance connecting to an AWS RDS PostgreSQL db.
Jira is becoming increasingly slow, sometimes it takes 5 minutes just to load the login page.
Any help on how to troubleshoot this is much appreciated.
Hi @Andrea C,
how did you configure you JVM parameters ? Could be a symptom of Garbage Collection taking a lot of time.
Check this page on how to have a look at your current settings.
On a side note: how many users are accessing the application and how many issues do you have on this instance ?
Let me know if you have any questions,
--Alexis
Hi @Alexis Robert,
I didn't configure the JVM parameters myself and it's also possible that they were never configured but just left the default ones.
I would say a maximum of 10-15 users can access the Jira Software application. There are currently 22 projects and 4064 issues.
What should I check first?
Thanks,
Andrea
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
you can check this page for more information on how to check your instance performance.
You'll need to check the logs and see if any errors are logged for example.
Let me know if you have any questions,
--Alexis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I check the garbage collections logs in /opt/atlassian/jira/logs/atlassian-jira-gc-2018-12-13_14-41-39.log.0.current
I can see some errors like:
2018-12-13T14:41:56.277+0000: 16.966: [GC (Allocation Failure) [PSYoungGen: 207782K->4809K(232448K)] 236808K->35394K(494592K), 0.0100766 secs] [Times: user=0.02 sys=0.00, real=0.02 secs]
2018-12-13T14:41:57.104+0000: 17.793: [GC (Allocation Failure) [PSYoungGen: 209097K->5719K(232960K)] 239682K->38744K(495104K), 0.0119325 secs] [Times: user=0.02 sys=0.00, real=0.01 secs]
2018-12-13T14:41:57.644+0000: 18.334: [GC (Allocation Failure) [PSYoungGen: 210007K->5175K(232960K)] 243032K->40791K(495104K), 0.0092484 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So it means that there is not enough space left in the JVM memory to perform a GC, I'd suggest increasing the JVM_MAXIMUM_SIZE by 512MB increments.
You can check this documentation on how to increase JVM memory for your instance.
Let me know if you have any questions,
--Alexis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes 768MB is the default, you could increase to 1024MB first. This is done directly on the Jira Server, in <jira-install-dir/bin/setenv.sh>by changing the setting in JVM_MAXIMUM_MEMORY from 768 to 1024
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok I can try that, even though I read that:
As a rule of thumb, if you have fewer than 5000 issues, JIRA applications should run well with the default 768 MB. Granting JIRA applications too much memory can impact performance negatively, so it is best to start with 768 MB, and make modest increases as necessary. As another data point, 40,000 works well with 768 MB to 1 GB.
Referenced from here.
And I have only 4000 issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.