JIra system slowness?

[Richard A. Michaels]

Hi All,
I've recently seen some slowness in my Jira Cloud system and have had one team mention the same observation. Could this slowness be the result of a bloated system?

I recently removed 500+ inactive workflows from our system and will be undertaking a thorough review of all other objects within the system.

Our current system is the result of two systems being integrated which resulted in duplicate statuses, custom fields and other objects.

We currently have 159 archived projects in the system.  These archived projects hold references to other objects such as custom fields, issue types, etc.

I've already proposed establishing a timetable for deleting archived projects from the system and will be working to establish a better maintenance routine for the system as a whole. 

I'm wondering whether the slowness is because of excessive junk in the system.

[John Funk · Accepted solution]

Hi Richard - How many custom fields do you have? And do all of them have a context (or the vast majority of them) with at least one Project and/or Issue Type? Meaning the majority are not all Global custom fields. 

[Richard A. Michaels]

@John Funk we have 614 active custom fields, only 1 doesn't have a context but there are 70+ which are not associated with a project.  Custom Fields is on my list of objects to review.  but I noticed all the fields associated with Checklist don't have a project associated with them so I've advised the team to be cautious about thinking a field is not used because it's not in a project.

[John Funk]

Yes, that's a lot of custom fields. A high number of custom fields in general will slow the system down in Cloud. Many would say it is the number of culprit. And then if you add that there are many that have a global context, that compounds the issue. 

We I first started using Jira, I had no idea about the impact of custom fields, and we just piled them on. Then one day we started getting 500 errors all the time. I plowed on through them, but it was very slow, time-consuming, and frustrating. 

I started doing some research and found out about the custom fields stuff. I went back through and added a context to 90% of the fields. And then no more 500 errors. And performance as a whole definitely improved and there were less complaints. 

[Matt Doar _Adaptavist_ · Accepted solution]

It's worth checking the number and type of apps you have installed as well, and whether some of them can be disabled

[JM Perrot · Accepted solution]

Hello @Richard A. Michaels 

One of my customers sent me the same experience, their instance is not very large and very well managed so I don't think it's due to a dusty instance but maybe just the connection between the Atlassian DC and you...

I'm curious to know whether this problem persists over time.

[Kevin Taylor]

I have a new instance with just two projects and only seven issues.

It's taking on average 10 seconds to respond to a mouse click and up to 20 seconds to reload after the click. I saw that there was a report of "degraded performance" yesterday. It says it is resolved, yet I'm still seeing these delays.