A customer with a trial license experiences JIRA becoming much slower after enabling / installing our add-on.
They experience the slowness on both opening the pages of our addon as well as opening pages of other JIRA functionality, like a JIRA dashboard.
The pages (like Dashboard.jspa) load in around 16-17 seconds, but we cannot see what actions are done under water. We think some kind of timeout is triggered on around 15 seconds, since the customer has a strict security/ internet network access policy.
We are currently thinking of two possible reasons:
A) The add-on has several menu items, which can be found below. Since it are menu items, these are the parts of our addon which are to be rendered for all JIRA pages.
B) JIRA could collect all resources (javascript, images and css) for all add ons for every page. This does not seems likely but we are not sure how JIRA does this.
Any other thoughts, why one add-on can influence the performance of the whole JIRA?
1) A system.top.navigation.bar, which uses a simple link factory.
<web-item key="menu_link" name="Instances" section="system.top.navigation.bar" weight="100">
<label key="menu.addon.label"/>
<link linkId="menu_link">http://www.website.com</link>
<condition class="com.plugins.jira.condition.HasViewRightsCondition"/>
</web-item>
<web-section key="menu_section_recent" name="Menu Section" location="menu_link" weight="10">
<label key="menu.addon.recent"/>
<condition class="com.plugins.jira.condition.HasViewRightsCondition"/>
</web-section>
<simple-link-factory key="dynamic-factory-current" name="Dynamic Link Factory" section="menu_link/menu_section_current"
i18n-name-key="Dynamic menu" weight="30" lazy="false"
class="com.plugins.jira.factory.DynamicLinkFactory"/>
2) A system.admin.top.navigation.bar
<web-section key="forecast-admin" name="menu-admin:Addon" location="system.admin.top.navigation.bar"
weight="100">
<label key="admin.section.name"/>
<description key="admin.section.description"/>
<condition class="com.plugins.jira.condition.JiraAdminCondition"/>
</web-section>
<web-section key="forecast-admin-main" name="menu-admin:Addon|Main Section" location="addon-admin"
weight="100">
<label key="admin.section.main.label"/>
<!-- Tooltip is used as a header for admin pages -->
<tooltip key="admin.section.main.header"/>
</web-section>
3) My JIRA home
<web-item key="wi-addon-jira-home-51" name="menu:My JIRA Home (JIRA 5.1+)"
section="system.user.options/set_my_jira_home"
weight="30">
<label key="s.wi-addon-jira-home.label"/>
<tooltip key="s.wi-addon-jira-home.tooltip"/>
<link linkId="addon-my-jira-home-set">/plugins/servlet/planning/mostRecentInstance</link>
</web-item>
Community moderators have prevented the ability to post new answers.
Thanks, we narrowed it down to one specific web-section. Which is not a must have functionality, and therefore can disable that temporarily. Thanks again!
I'd start by disabling all the modules in the plugin (i.e. all three plugin points you mention) and then re-enable them one by one, testing for the slow-down. That will probably nail it to one of the three.
The usual culprit in this kind of slow-down is repeated permission checks though, so I'd try recompiling the plugin without them in sections 1 and 2, and see if the slow-down still happens.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.