Heads up! On March 5, starting at 4:30 PM Central Time, our community will be undergoing scheduled maintenance for a few hours. During this time, you will find the site temporarily inaccessible. Thanks for your patience. Read more.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Jira Service Management Asset Sizing Guide

Mirek
Mirek
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
February 26, 2025

Hello, 

There is plan to load a large number of objects / relations to Jira Asset and I am wondering how JIRA connected with JSM (Assets) are actually currently sizing..

I am aware of good performance testing documentation for JIRA like this

https://confluence.atlassian.com/adminjiraserver0904/performance-and-scale-testing-1188769020.html

but it is not tested with Assets objects.. 

looking around and not seeing much information but I know that using Assets requires a lot of memory due to a fact that is not using Lucene but a different library and store all the indexes there and building/loading it on startup.. 

https://confluence.atlassian.com/servicemanagementserver0513/installing-assets-1345822420.html

Is someone aware of any best practice / sizing guide for Assets so that it could be easier to plan before loading large date set? 

 

 

Answer
Watch
Like # people like this
80 views

0 answers

Suggest an answer

Log in or Sign up to answer
groups-icon
Enterprise
TAGS
AUG Leaders

Atlassian Community Events

    See all events