Page Load Performance - Release 10.75

[#1]

There were some issues that blocked us from publishing results for version 10.74 and delayed the publishing of version 10.75. For transparency we would like to highlight the issues we encountered:

• We had issues with the original website and database. This required creation of a new test site and database.

• Once the new database was in place issues with the data between the old and new databases caused test failures.

• We ran into issues requiring application support during our test expansion and refactoring.

• The test expansion and refactor added more steps to each test and provided uniformity between different work item tests.

Also in the current article, some test results won`t be shown (please refer to a table with results) and we are working on returning them in future publications.

Page Load Trends

This graph shows Jira Align page load performance trend version to version. The x-axis shows the areas under test color-coded to the production version. The y-axis shows page load times in seconds.

Page Load Times in Seconds

This table shows Jira Align page loads time in seconds. Our goal is for all pages within the application to load within three seconds. The cells are color-coded to easily show where we beat, meet, and miss our goals.

Data profile

We are actively working to expand our performance dataset and will update this section as we add more work items and hierarchies.

Work Items

• Themes: 40

• Epics: 400

• Capabilities: 1,600

• Features: 6,400

• Stories 64,000

• Objectives: 586

Work Hierarchies

• Portfolios: 1

• Programs: 4

• Teams: 415

• Program Increments: 99

• Sprints: 1,333

• Users: 50,500

Test Environment

Hardware of system under test

• ALB configured for IP sticky

• Web servers: AWS EC2 t2.large; default storage subsystem; default network

• Database Server: db.r4.xlarge; SQL Server Engine version 14.00.3223.3.v1

For more context how we gather our performance metrics please visit - Jira Align Performance Benchmark  

[Gonchik Tsymzhitov]

Now looks like a new feature was implemented :) 

It will be good to know the affected a new functionality