Agile Story Map Performance query

We have been trialling the story map plugin over the last couple of months on a download installation of Jira and like it. I have a concerns about deploying to our production Jira instance in relation to performance.

I would like to know if you have any information on the performance of your story map plugin at scale?

We have a large Jira instance (Jira v5.1.6 with the Greenhopper plugin v6.0.5 and some other plugins. We are planning to upgrade to Jira 6.1 and the latest Greenhopper plugin in the next 6 weeks.)

  • Issues - 705167
  • Projects - 548
  • Custom Fields - 589
  • Workflows - 109
  • Attachments - 675945
  • Comments - 2104831
  • Users - 5254
  • Groups - 314

I would like to know what type of footprint this plugin may add to my Jira instance:

  1. Does it add its own data to the Jira lucene indexes - If so how much do they grow by typically?
  2. Should I consider increasing JVM RAM if I proceed with purchasing your plugin?
  3. Does it consume any disk space on the server side?
  4. How many issues can a story map handle before there is a notable performance degradation either with the story map or Jira or both?
  5. Does the number of story maps affect the performance?
  6. Does the plugin write many records to the database or is the story map calculated dynamically from the Epic/Theme field?

If you have no performance data for the plugin - can you tell us what type of things (that may affect performance) we should test in the plugin (on a test instance of Jira) before we deploy this to production?

Thanks,

Cyril Egan

1 answer

1 accepted

This add on adds no own custom fields or any additional data/indexes to your installation but uses only existing services. All the business logic is implemented at the client side – therefore no performance impact at the server side is expected! To show up the map once it needs one JQL- query – after that only little data is exchanged with the server.

Your questions in detail:

  1. 1) No
  2. 2) No
  3. 3) No
  4. 4) The Map only shows issues of type story and epic. If your map contains more than 500 - 750 stories (only stories count!), your browsers (client not server) performance could be influenced.
  5. 5) No
  6. 6) No

This add on can be used at your described configuration without hesitation and without any additional resources.

Let me know if there is anything else I can do for you!

Florian

Thanks Florian - This answers all I need to know. We will be proceeding with the plugin in due course :-)

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,329 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot