This document summarizes a presentation about performance testing tools used at JP Morgan Chase for their JIRA instance over several years. It discusses the tools they used - Load Runner, JMeter, nGrinder, and more recently Gatling with InfluxDB and Grafana. It provides a scorecard comparing the tools and demonstrations of using Gatling and viewing results in Grafana. Key takeaways are to pick the right tools for the job, know your constraints and goals, and reach out for help from Atlassian and partners.

1. #atlassian

2. JIRA Performance Testing in Pictures
Measuring Big JIRA at JP Morgan Chase
Ed Bukoski • Lead Architect • JP Morgan Chase • @EBUKOSKI
Michael March • Senior Consultant • Isos Technology • @COWMIX

3. Introduction
• Speakers
• Michael March (@cowmix)
• Senior Consultant
• Isos Technology
• Ed Bukoski (@ebukoski)
• Lead Architect
• Developer Collaboration Tools Group

4. NOTES:
• This file is set to a 16:9 aspect ratio, which works for
Summit Preview Day, Training Day, and Summit’s
Session Talks.
• Make sure you’ve downloaded and loaded the
fonts, which should have come with this
presentation file. The fonts are: Helvetica Neue
• Some page template will have notes with instructions
to the right of the art board.
• You should’ve also received an “Assets” file with icons
and graphic assets and color palette. Updated
“meeple” avatar graphics are coming soon.
• This deck has been made slightly darker than average
because the projector will lighten everything by 10 or
15% and add a little extra contrast. If you create new
assets, keep this in mind.
Read me
Introduction
• JIRA Performance Testing in Pictures
• Performance testing is critical
• The right tools are important:
This presentation deck is designed as a canvas for you to craft your stories.
"
The best presentations are focused on connecting to the audience by
enhancing and punctuating your stories rather than describing it with text.
"
With • this Generate in mind, the load
presentation template is filled with slides for using
images, videos, screenshots, and large punchy text.
"
• Measure
While • we Evaluate
did include a few slides with small text and bullets we hope you only
use those sparingly when necessary and avoid creating SLOCUMENTS (noun:
the • combination Communicate
of document style prose on a presentation slide). Slocuments
force your audience to multi-task by reading and listening at the same time –
this typically results in a drop in engagement.
"
Go on and create the best presentation of your lives!
• Four years of performance testing tools at JPMC
• Current tools

5. JIRA at JP Morgan Chase
Instances
19
Projects
7,059
Issues
2,427,650
Users
55,394
Servers
76

6. 2011
4.2
2013
5.1.8
2014
6.2.6
2012
4.4.5

7. HP Load Runner
• Used for testing JIRA 4.2.2 and JIRA
4.4.5
• JPMC Standard load testing tool
• Centralized performance testing team
• “Ivory Tower” model

8. Static
Nice
SharePoint

9. ? Drill Down?
Noisy

10. Scorecard
Load Runner
Compare performance between runs
X
Easy publishing
X
Correlated client and server data
X
Easy report generation
X
Easy to execute/rerun tests
Drill down to individual tests
Open source
Tests available from Atlassian
Control tests and data
Web based execution and reporting

11. 2011
4.2
2013
5.1.8
2014
6.2.6
2012
4.4.5

12. Apache JMeter
• Used for testing JIRA 4.2.2, 4.4.5, and
Confluence 3.3
• Open source
• Easy to get started
• Stock testing scripts available from
Atlassian

13. Run
Some…
…assembly…
…required.

14. Excel charts
Confluence

15. Scorecard
Load Runner
JMeter
Compare performance between runs
X
Easy publishing
X
Correlated client and server data
X
Easy report generation
X
Easy to execute/rerun tests
X
Drill down to individual tests
Open source
X
Tests available from Atlassian
X
Control tests and data
X
Web based execution and reporting

16. 2011
4.2
2013
5.1.8
2014
6.2.6
2012
4.4.5

17. nGrinder
• Used for testing JIRA 4.4.5 and 5.1.8
• Open source
• Easy to get started
• Stock testing scripts available from Atlassian
• Web based

18. Python/Groovy
SVN Built-In
Test Single

19. Agents/Users
Ramp Up
Host Capture
Duration/Count
Agents

20. Client
Server

21. Scorecard
Load Runner
JMeter
nGrinder
Compare performance between runs
X
Easy publishing
X
X
Correlated client and server data
X
Easy report generation
X
Easy to execute/rerun tests
X
X
Drill down to individual tests
Open source
X
X
Tests available from Atlassian
X
X
Control tests and data
X
X
Web based execution and reporting
X

22. 2011
4.2
2013
5.1.8
2014
6.2.6
2012
4.4.5

23. Gatling/InfluxDB/Grafana
• For JIRA 6.2.6, we wanted a testing suite
that could do it all
• nGrinder was good, but it still forced us to
manage client and server data separately
• Multiple tools approach
• Gatling
• InfluxDB
• Grafana

24. Gatling/InfluxDB/Grafana
sysinfo_influxdb

25. Scenarios, DSL
IDE (IntelliJ)
Test
VCS of our choice

26. Normal job/plan
History
Trend

27. Demo: Starting the Test

28. Demo: Viewing Data in Grafana

29. Demo: Viewing Data in Gatling

30. Demo: Creating Charts In Grafana

31. Client
Server

32. Scorecard
Load Runner
JMeter
nGrinder
Gatling, InfluxDB,
Grafana
Compare performance between
runs
X
X
Easy publishing
X
X
X
Correlated client and server data
X
X
Easy report generation
X
Easy to execute/rerun tests
X
X
X
Drill down to individual tests
X
Open source
X
X
X
Tests available from Atlassian
X
X
Control tests and data
X
X
X
Web based execution and
reporting
X
X

33. Performance Factors
• Factors that impact JIRA performance
• Issue Count
• Custom Field Count
• Permissions
• Concurrent Users
Source: https://confluence.atlassian.com/display/ENTERPRISE/Scaling+JIRA

34. Key takeaways:! #atlassian!
• Pick the right tools for the job• Know your constraints
• Know your goals
• Reach out
• Atlassian
• Atlassian Partners
• User Groups

35. Thank you!
And a special thanks to George Simpson,
Lead Architect, JP Morgan Chase, for
helping us put this presentation together!