Higher CPU load after upgrade tu 8.14

[Application Operation - Jira]

Hello!

We recently upgraded our Jira installation from 8.8.1 to 8.14.0.
We noticed immideatly after the upgrade an increase of CPU load for about 15%.

I have not found any clear reason for that. Might be also due to added functionalities in Jira itself. Is there anything known?

We had even more increased Load on the develop and test system, but due to much lower load there we did not notice that immideatly.

Regards

[Daniel Ebers]

I am wondering is the load is going down after some amount of time?
Right after the start of Jira the load is somewhat high, we have seen this in several cases during the years, but it goes to a healthy level within minutes.

In case the load stays high(er than you expect it to be...) - there are several things to check. In first instance if there are any Apps involved (probably outdated ones) but you could check also for anything else changed - like scripts not bevahing correctly anymore (if you use some) or accesses to REST API that could now produce an error or some strange behaviour.

Have you checked the logs so far alongside with the usual troubleshooting documentation?

https://confluence.atlassian.com/jirakb/troubleshoot-performance-issues-in-jira-server-336169888.html

Regards,
Daniel

[Application Operation - Jira]

Hello

No, the load is not going down. The average load is constantly about 15% higher then before the update. We could not find any reason for that till now. Installed additional apps are all up to date. Logfiles look normal.

[Daniel Ebers]

This all might need further and in-depth inspection of your setup, much more than what is possible remotely via Community.

But one thing just comes to my mind when you said the load rises unexpectedly after an upgrade while you did not change something fundamental in your installation.

You could check if settings in your setenv.sh (Linux) or setenv.bat (Windows) were not carried over causing now this effect because of (just a guess though!) not optimal JVM settings for memory and/or garbage collection.

From a theory when the file was "forgotten" to bring back and Jira is now running with default values the system might show different behaviour for memory consumption and/or CPU load (as a result).