Jira Performance Tests (JPT) beta is now available

performance

#1

We’re excited to announce that our Jira Performance Tests beta tooling is open for early access!

We built Jira Performance Tests (JPT) to benchmark each release of Jira, helping us prevent performance regressions over time. JPT helps us make informed decisions in improving the performance and scalability of Jira, ensuring that it stays enterprise-ready. We’re now releasing JPT to help app developers like you test the performance impact of your apps on Jira.

JPT offers a comprehensive and fully orchestrated testing framework for Jira apps. It can provision Large-sized Jira instances, simulate user load, and collect performance data all from one command. We designed JPT’s first public release to help you study how your app performs on a typical enterprise Jira instance.

We hope you find JPT as useful as we do in improving the performance and scalability of your apps. We encourage you to test it, tweak it, and provide feedback - we’d love to hear how we can help you build better apps. Let’s TEAM up to achieve even more!

Head over to:

go.atlassian.com/jpt

If you need help, run into problems, or have a suggestion, go to feedback page in our docs.

Have fun testing!
The Server Performance Team

FAQ

Q1: What capabilities are you including in this release of JPT?
A1: JPT is an all-code solution, giving capable developers the flexibility to customize it for their own purposes. It delivers an official standard benchmark for Jira, simulating heavy user traffic over a Large-sized data set on AWS infrastructure to detect any scaling issues. You can find more details in our documentation.

Q2: Why are you releasing JPT?
A2: We want to help app vendors like you build products that run reliably at a large scale. Our goal is to improve JPT so that it can:

  • Verify if your app’s current versions are stable, performant and scalable with the growing customers’ instances,
  • Ensure that new versions of your apps do not introduce any new performance regressions, and
  • Produce credible test results with your customers, increasing their confidence in the quality of your products.
    It’s an iterative process requiring your contribution. We want to invite you in shaping JPT’s future! Feel free to tweak JPT and contribute to it’s core functionality to run tests better suited for your apps. We’re here to help you through this process.

Q3: Does JPT address all of the guidelines for the Data Center Apps development program?
A3: The short answer is: No.
However, JPT’s tests meet some of the requirements, namely:

  • Use of a Large data set
  • Control number of nodes in the cluster
  • Contrast performance across 1/2/4 nodes
  • Contrast performance with/without app
    You can also use JPT to provision clustered Data Center instances. To learn more, see the guidelines for Data Center app development.

Q4: Do I need to pay to use JPT?
A4: No! JPT is a free, open-source project distributed under the Apache 2.0 license.

Q5: Are you open for contributions to JPT?
A5: Absolutely! JPT is open for contributions and is as much an opportunity for you to learn from us as it is for us to learn from you. You can now directly influence how the platform for your Apps is being tested and maintained to support your business.

Q6: Will customers get JPT too?
A6: We’re also going to open JPT to our customers. We’ve created a separate module to help them benchmark their existing staging environments. This can help them study an impact of planned environment changes to their instance’s performance and in the future impact of projected growth.
If you are also a solution partner, feel free to use JPT in addressing customer questions about the performance of their instance.

Q7: What versions of Jira does JPT support?
A7: JPT supports all Jira Software versions starting from 7.2.0 version onwards.

Q8: Are there any plans on publishing a similar performance testing tooling for Confluence and Bitbucket?
A8: In long run, we’re considering creating a new performance testing tooling for Confluence and Bitbucket that would replace the existing E3 solution. While on this topic, we would love to hear what you think about this idea. Would you need it? If so, why? What problems would you like it to solve for you? Follow this link and share your feedback!


pinned #2

#3

Thanks for this. It looks great.
There’s no mention of loading custom data into the Jira Instances provisioned on AWS? Is this possible?

Cheers.