Maintaining Large Jira Assets Management Instances

[Mirek]

Hello, 

In relation to this question - https://community.atlassian.com/t5/Enterprise-questions/Jira-Service-Management-Asset-Sizing-Guide/qaq-p/2956366 where I look for specific testing results.. 

I am looking for information how Asset actually behave on large instances that are in real use, when it would impact performance and how to archive and manage objects over time so that everything would be working as expected.. 

Is there someone that is using a big instance with a lot of Assets that can share best practices (maybe some real numbers of objects and issues)? 

Thanks!

[Andrea Robbins]

I've never experienced super huge asset instances before from all clients I have worked with. I would say at most 20-25k assets in Cloud. I haven't noticed any performance issues with the Jira instance itself, but there are a few things I have noticed (please note these are my observations only not really backed by any evidence and could be a result of slow internet or something else):

- I noticed that the number of assets doesn't really make a difference in general but the number of assets within one object type makes a difference. Like I could have thousands of assets, but if they are split into many object types, no big deal. But if all 20k are in one object type, then the load time of that object type page tends to take longer or doing AQL searches. 

- I also noticed that the more objects that are allowed to be used within an Assets field, the longer it takes for the asset to be searched/found. If you limit the AQL a good amount for the Asset field, the search is much faster.

- This is just best practice imo, but another thing that makes a difference comes down to the attributes - are they unique? are there many attributes (meaning over 25)? do you have an object attribute that allows the max 20,000k objects to be selected? That's going to slow things down doing AQL searches. I recommend any many-to-many relationships to be split out into it's own object instead of having like 30 referenced objects within an attribute unless absolutely necessary.

Hopefully this was helpful! If someone had ways to measure the performance when it comes to assets that would be amazing in Cloud, but these are just my observations.

Andrea