You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
2020 has been a really fruitful year in the life of Timetracker. While we were heavily focusing on adding new features and improving the quality of the cloud version, we definitely didn’t want to forget the server and data center versions either. We also keep updating it in the future, despite the announcement of the Server platform ending. Everit has been developing Timetracker Server & Data Center version for years so we can honestly say that it already has all the must-have features. Of course, there is always room for improvement but for mature software, you have to refactor and update the existing code with better solutions from time to time to keep the application stable. It is always easier to add new things if you build on a strong foundation.
That’s why we dedicated the whole 2nd quarter of 2020 to completely rework the reporting feature of Timetracker. We wished to increase the speed of all the reporting options. As bigger and bigger customers start to use our solutions, we also want to make sure that they won’t experience any limitations. Want to generate a report for a whole quarter? Sure! Go ahead!
We ran several tests to compare the reporting speed of Timetracker version 4.7.4 (before refactor) with 4.8.0 (after refactor). Let’s see what we managed to achieve in numbers.
We started to test with smaller numbers and scale it later. Firstly, we added 10 projects that contained 100 Issues each. We added 2 years to the time interval filter. Overall, that meant 19,307 worklogs.
We ran three individual tests to make sure the results are correct. They are shown on this first diagram:
As you can see in the diagram, for this size the speed was already okay, around 1-2 seconds. The slowest one was the Details reporting view, where we show all the worklogs individually (in this case almost 20k). Before the rework the time was between 5-6 seconds and after, it is less than 1 second! Pretty amazing, huh? But wait, we have much more to show!
Let’s do more interesting things! This time, we added 25 projects, all of them contained 200 Issues and the date range was 3 years. The total number of worklogs was 72,101.
The result is shown in the diagram below:
As you can see, with this data size, the Timesheet view started to struggle before the refactor. It needed around 80 seconds to provide the requested information. The details view also had issues. But the result of version 4.8.0 is just amazing! Less than 5 seconds needed for both of these views.
It looked like we were still able to ramp up the reporting values, so we tried to report 240,121 worklogs at once.
You can see the numbers for this test case here:
Before the refactor, for this size Timetracker reporting needed about 2.5 min on average to provide a result. For Timesheet, it needed more than 6 minutes! You could grab a coffee while you were waiting for the report. Noone would wait that long for some data nowadays. No worries, the reworked version is able to handle that much amount of data within 10 seconds!
After all that, we wondered what is the limitation of Timetracker reporting option. Eventually, we added almost 2 million worklogs to the query.
Needless to say, it was impossible to get results for that much data before the refactor. Even version 4.8.0 needed around 70 seconds to process. So in that case, we advise you to narrow down your filters just a little bit. :)
If your daily work requires you to check or report an excessive number of worklogs in Jira – that you cannot filter further – you should definitely try Timetracker. It will save a lot of time and it will make your life much easier!