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
Next: Root
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
Today, I would like to collaborate with the community about the real usage of Insight for Jira in world instances and provide my feedback.
As we know on Cloud, Insight for Jira has a limit of 400k objects for Enterprise subscription, 60k for other situations on the Cloud. So for the on-premises releases Insight for Jira has not any limitation, except heap size requirement.
Objects in Insight | JVM memory |
~10.000 | 4Gb |
~100.000 | 8Gb |
~500.000 | 16Gb |
~1.000.000 | 32Gb |
~2.000.000 | 64Gb |
~5.000.000 | 128Gb |
Note the next info: remember to always test the memory consumption in a test environment for a huge data set, because it's not always the number of objects, but the content of the object attributes as well at play.
i.e. one of my instance has
At the moment, it works well, based on the performance metrics we can meet soon with limits, then I will be happy if vendor will review app and reduce memory usage.
You can fill that form, https://forms.gle/LCRKPbVB11YCP6xA6
after we can review the stats of usage. (SQL queries for getting stats )
Conclusion:
Links:
Gonchik Tsymzhitov
Solution architect | DevOps
:)
Cyprus, Limassol
174 accepted answers
1 comment