Rate this page:
Always consider how your app affects the performance of large DC. These are DC that host large data sets and sustain a significant amount of traffic.
Ensure that you have appropriate indexes set up on all tables introduced by your feature or app. Wherever possible, filter data in database queries, rather than relying on in-app filtering, as the latter may require loading and discarding lots of data.
Finally, always test your feature or app on a Data Center instance with a large data set. The following subsections provide guidelines on what we consider a large instance for each product.
A Bitbucket DC with these dimensions is considered large:
| Dimension | Baseline |
|---|---|
| Projects | ~25 000 |
| Repositories | ~52 000 |
| Users | ~25 000 |
| Pull Requests | ~1 000 000 |
| Total files number | ~750 000 |
When testing your app on an instance with this dataset, ensure that users can still:
A Confluence DC with these dimensions is considered large:
| Dimension | Baseline |
|---|---|
| Pages | ~900 000 |
| Blogposts | ~100 000 |
| Attachments | ~2 300 000 |
| Comments | ~6 000 000 |
| Spaces | ~5 000 |
| Users | ~5 000 |
Some of these dimensions use the upper limit of the content and traffic metrics for large instances in Confluence Data Center load profiles.
When testing your app on an instance with this dataset, ensure that users can still:
A Jira DC with these dimensions is considered large:
| Dimension | Baseline |
|---|---|
| Attachments | ~2 000 000 |
| Comments | ~6 000 000 |
| Components | ~2 500 |
| Custom fields | ~800 |
| Groups | ~1 000 |
| Issue security levels | 10 |
| Issue types | ~300 |
| Issues | ~1 000 000 |
| Priorities | ~5 |
| Projects | ~500 |
| Resolutions | ~34 |
| Screen schemes | ~200 |
| Screens | ~200 |
| Statuses | ~400 |
| Users | ~21 000 |
| Versions | ~20 000 |
| Workflows | ~50 |
Some of these dimensions use the upper limit of the metrics for large instances in Jira Data Center size profiles.
When testing your app on an instance with this dataset, ensure that users can still:
A Jira Service Management DC with these dimensions is considered large:
| Dimension | Baseline |
|---|---|
| Attachments | ~2 000 000 |
| Comments | ~2 000 000 |
| Components | ~1 500 |
| Custom fields | ~400 |
| Organizations | ~300 |
| Requests | ~1 000 000 |
| Projects | ~200 |
| Screen schemes | ~500 |
| Screens | ~3000 |
| Users | ~21 000 |
| Workflows | ~700 |
Some of these dimensions use the upper limit of the metrics for large instances in Jira Data Center size profiles.
When testing your app on an instance with this dataset, ensure that users can still:
A Crowd DC with these dimensions is considered large:
| Dimension | Baseline |
|---|---|
| Users | ~100 000 |
When testing your app on an instance with this dataset, ensure that users can still:
A Bamboo DC with these dimensions is considered large:
| Dimension | Baseline |
|---|---|
| Users | 2000 |
| Projects | 100 |
| Plans | 2000 |
| Remote agents | 50 |
When testing your app on an instance with this dataset, ensure that users can still:
Rate this page: