Very high memory utilization by Atlasian JIRA

On Server JIRA is consuming more than 9 GB of RAM. this is after, i restarted.

Before restart, it was consuming more than 15GB due to which i was informed by Server team for this.

Please guide me, how to find out the reason like which part of JIRA is causing so much utilization.

Is there any task manager like thing inside JIRA ?

Capture1.PNG

 

Regards,

Deepak

2 answers

1 accepted

1 vote
Accepted answer

JIRA (in fact, most Java applications) will quite happily use whatever memory you choose to let it have.  If use of too much memory is an issue, reduce the maximum allocation.  Of course, there is a minimum amount it will need, depending on the kind of loads you put on it.

For information on how much memory you might want, start at https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html and then have a look at Dan's talk on it (still valid concepts, although numbers may be a little different) - https://summit.atlassian.com/archives/2013/inside-the-massive-team/the-not-so-dark-art-if-atlassian-performance-tuning

Thanks Nic. Answer was very informative.

Following is the load on my JIRA, i would be very thankful if you can suggest a required hardware configuration:

  • Projects : 6
  • Issues: 100670
  • Total Users: 17031, out of which 503 are Service Desk users and remaining 16528 are Service Desk customers
  • Custom fields : 52

Currently, Server has 32 GB of RAM.

hi fellas, we have the same issue.

8GB of ram and almost all is consumed.
when i log to ssh i got an watchdog error

kernel:NMI watchdog: BUG: soft lockup - CPU#6 stuck for 24s! [java:16001]

 

reason: systemd-logind killed by SIGABRT
time: Mon 11 Feb 2019 04:36:52 AM -02
cmdline: /usr/lib/systemd/systemd-logind
package: systemd-219-62.el7_6.3
uid: 0 (root)
count: 4
Directory: /var/spool/abrt/ccpp-2019-02-11-04:36:52-4892

id dbc1f6f99d42fe0717d1f925ef299fbfb0564227
reason: systemd-journald killed by SIGABRT
time: Thu 21 Feb 2019 04:02:41 AM -03
cmdline: /usr/lib/systemd/systemd-journald
package: systemd-219-62.el7_6.3
uid: 0 (root)
count: 1
Directory: /var/spool/abrt/ccpp-2019-02-21-04:02:41-29702

id 12a64eb7351d516a0e47152acdcfc8f250f28166
reason: systemd-journald killed by SIGABRT
time: Sun 10 Feb 2019 04:28:32 AM -02
cmdline: /usr/lib/systemd/systemd-journald
package: systemd-219-62.el7_6.3
uid: 0 (root)

 

any tip?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

251 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you