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
This example comes from internal development, in fact, this is often the case with applications from the marketplace.atlassian.com.
One morning, looking at the charts, I saw how slow and repetitive the requests are, which often indicate automation and integration.
Having clicked on the requests, I saw that almost all of them refer to the rest endpoint below.
And right away by clicking on the flamegraph, we can easily find the roots, all these heavy requests and allocated memory.
Then I got a trace to the method, and I see that 80 percent comes fromIssueToJiraExtranetIssue method.
Since this is a jar file by IntellIJ Idea, we find interesting points. In the following piece of code,
Line 422, issueRequest.getMax () is not a desirable practice
Line 427 points to the jiraExtranetIssue class, which has a huge number of fields.
As a result, the next step was refactoring class fields, review loop.
As optional info, please, checkout the next article.
https://www.csd.uoc.gr/~hy252/project_old/performance.pdf - this one describe the fundamental steps, of course in the new JDK build better and run in JRE as well.
Next example will be related to the one of apps from the marketplace, once the vendor accepts.
I hope it was interesting, feel free to ask questions