Some Jira timesheet performance measurements for reference

Owned by Deniz Oğuz
Apr 15, 2024
1 min read

Jira Timesheet performance depends on number of worklogs/users/issues/worklog attributes and several other factors. Time to retrieve a report depends on the number of users, issues, worklogs and worklog attributes on the report. Number of different users and issues has more effect than number of worklogs.

Here some samples:

Single node DC on Laptop 650.000+ issues, 1.000 users, 774.000+ worklogs:

  • User timesheet with 129 issues and 129 worklogs < 2 seconds

  • Project timesheet with 1 project, 575 users, 453 issues, 609 worklogs < 3 seconds

  • JQL timesheet with 9 project, 24 users, 240 issues and 1182 worklogs < 4.5 seconds

  • JQL timesheet with 12 projects, 29 users, 698 issues and 5113 worklogs < 6 seconds

  • Project timesheet with 1 project, 20 users, 3000 issues and 15000 worklogs < 25 seconds

  • Project timesheet with 1 project 592 users, 4300 issues and 21370 worklogs < 33 seconds

Single node DC on AWS (db.m5.xlarge and c5.4xlarge) 1.2+ Million issues, 21.000 users, and 1.6+ Million worklogs:

  • JQL timesheet with 10 projects, 1797 users, 993 issues and 1879 worklogs < 15 seconds

  • JQL timesheet with 1 project, 1797 users, 2770 issues and 5211 worklogs < 54 seconds

 

Other than performance of the Jira server, your browsers performance also affects user experience. If you are retrieving a timesheet for a large period (large number of columns), and also there are large number of rows (for example, number of users if you group by user), your browser may have difficult time displaying results.