I'm trying to get some feedback on the system requirements when using the Tempo Planner plug-in in JIRA.
The TEMPO site sent me here to ask a questions since I only have a trial license.
We are running the following in a VM with 2 vCPUs, 8GB of memory, with a 3GB JVM, against an Oracle 11g database: JIRA v6.1.9, JIRA Agile v184.108.40.206, Tempo v2.2, Tempo Core v2.2, Tempo Teams v2.4.3, Tempo Planning v2.0.1
We are not running out of memory or crashing, but at times, for 30-120 seconds, the whole instance gets bogged down. We've blamed it on GC in the past, but we are wondering if Tempo Planner is the culprit. The users that are evaluating the plug-in tell me the screens load very slow (maybe 30-120 seconds).
I suggest that we move this support to our Tempo Support System rather than following up here as me might need to view your JIRA logs. This also promotes faster response times. Please visit the page below for further information
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs