I've been looking into the performance issues of Jira within a docker container on a CentOS 7 server. This machine has 16GB of RAM and 8 CPUs. I've noticed that the Jira docker instance is consistently spiking to ~120+% CPU usage using the "docker stats" command. I ran the following commands:
#Identify the JIRA application PID by using the below command
JIRA_PID=`ps aux | grep -i jira | grep -i java | awk -F '[ ]*' '{print $2}'`;
#Then run the following command - it generates 6 snapshots of CPU usage and thread dumps with 10-second intervals for a minute.
for i in $(seq 6); do top -b -H -p $JIRA_PID -n 1 > jira_cpu_usage.`date +%s`.txt; jstack -l $JIRA_PID > jira_threads.`date +%s`.txt; sleep 10; done
This captured some snapshots of CPU usage and I noticed that the process pool-####-thre or MVStore backgro is what is causing the CPU usage spiking.
How can I prevent these processes from spiking so often so I can eliminate the latency within Jira? Or is there anything else that I can do to stop Jira from using up so many CPU resources?
