Why do we need to change the Java Version to 11 and provide a feedback to vendor?

Hello, 

 

Today I would like to provide my feedback about using JDK 11 and JDK 8. My reason for  that is motivating the other person to go forward with new releases, instead of waiting for the more stable and more robust release, who will test and provide if everyone will wait?

  

That story of performance depute of JDK 11 vs JDK 8, as that depute started from that article (reasons to stick Java 8) with one of member of Atlassian community, so fully correct way is measure one your instance. 

 

So what about to make a real performance testing on our copy production Jira? As Atlassian team provided a pretty simple toolkit to make performance tests (performance-toolkit), sure we can to it.

 

My setup based on the next things:

  1. Copy of production Jira 8.5.4 on dedicated VM
  2. Changing the Java version via JAVA_HOME variables with the same arguments and GC strategy (G1GC):
[[gonchik.tsymzhitov@jirasandbox1 java]# /usr/java/latest/jre/bin/java -version

openjdk version "1.8.0-builds.shipilev.net-openjdk-shenandoah-jdk8"

OpenJDK Runtime Environment (build 1.8.0-builds.shipilev.net-openjdk-shenandoah-jdk8-b605-20200323)

OpenJDK 64-Bit Server VM (build 25.71-b605-20200323, mixed mode)
[gonchik.tsymzhitov@jirasandbox1 ~]$ /usr/java/latest/bin/java -version

openjdk version "11.0.7" 2020-04-14

OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)

OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.7+10, mixed mode)
  1. I used the performance toolkit with the next variables:
    concurrency: 200
    test_duration: 45m

You can play with concurrency for the more interesting results, for understanding the exist situation is enough to check with concurrency 200.

 

So here we go to see a process:

image.png


After waiting 2 hours I got the next results for the standard of tests from performance toolkit.

For the testing used the below tests:

jmeter_login_and_view_dashboard

jmeter_view_issue

jmeter_view_dashboard

jmeter_search_jql

jmeter_open_quick_create

jmeter_create_issue

jmeter_view_backlog

jmeter_view_kanban_board

jmeter_view_project_summary

jmeter_view_scrum_board

jmeter_open_comment

jmeter_open_editor

jmeter_save_comment

jmeter_save_edit

jmeter_browse_projects

jmeter_browse_boards

selenium_login:open_login_page

selenium_login:login_and_view_dashboard

selenium_login

selenium_browse_projects_list

selenium_browse_boards_list

selenium_create_issue:open_quick_create

selenium_create_issue:submit_issue_form

selenium_create_issue:fill_and_submit_issue_form

selenium_create_issue

selenium_edit_issue:open_edit_issue_form

selenium_edit_issue:save_edit_issue_form

selenium_edit_issue

selenium_save_comment:open_comment_form

selenium_save_comment:submit_form

selenium_save_comment

selenium_search_jql

selenium_view_scrum_board_backlog

selenium_view_scrum_board

selenium_view_kanban_board

selenium_view_dashboard

selenium_view_issue

selenium_project_summary

selenium_log_out

So based on that you can see a graph of tests:

image.png

image.png

Let’s have looked a deep into main functions like create issue and view issues:

image.png
image.png


image.png

 

Conclusion:

 First of all, a big thank to the Atlassian Team who made so easy to go the performance toolkit. Based on the measure, I would say for one of the instances the JDK8 and JDK11 are not clear, as most of the G1 improvements made with backports, but if more and more software will go forward, hence industry will go forward.

Hence I want to say a big thank you for the developers for the tuned Atlassian suite to be with JDK11. Hence most of my instance works on adopt JDK 11 with Shenandoah GC. I hope they want to improve themselves software as soon as possible with minimum of headache of dependencies, legacy and EOL, license agreements...

I think most of developers want to remove a legacy things, as we are end-users, we can provide more and more feedback and do upgrade, otherwise we need to go Cloud :).

 

Disclaimer:

Please, measure before upgrade your system or read more improved things from JEPS. 

References:

The next links will help you to migrate:

Cheers,

Gonchik Tsymzhitov

4 comments

Comment

Log in or Sign up to comment
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 7, 2021

Looks like jdk 11, still not popular. 

As I see too many companies will be still on JDK 8

Matt Doar
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 15, 2021

Is anyone using JDK 11 in production with Jira? Confluence?

Like Gonchik Tsymzhitov likes this
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 15, 2021

@Matt Doar  I use adoptJDK 11 with G1GC, and with Shenandoah. If we have leakage, prefer to use Shenandoah. 

The cause is pretty clear. 

  • Jira 8.5, 8.13, 
  • Confluence 7.2, 7.4. 
  • Bitbucket - latest version
  • Bamboo 7.2, 
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 16, 2021
TAGS
AUG Leaders

Atlassian Community Events