Atlassian Marketplace Developer

Atlassian Marketplace Developer

Last updatedJan 20, 2021

Rate this page:

Testing your app on a large DC

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.

Dimensions of a large Bitbucket DC

A Bitbucket DC with these dimensions is considered large:

DimensionBaseline
General
Users15,000
Groups5,000
Projects30,000
Repositories75,000
Pull requests
Open100,000
Closed5,000,000
Comments on pull requests10,000,000
Nodes5
Continuous load for the baseline in the performance smoke test
Clone8 concurrent; 30/minute
Fetch8 concurrent; 800/minute
Push8 concurrent; 10/minute

When testing your app on an instance with this dataset, ensure that users can still:

  • List projects
  • List project repositories
  • Browse pull requests
  • Browse diffs
  • Comment on pull requests

Dimensions of a large Confluence DC

A Confluence DC with these dimensions is considered large:

DimensionBaseline
Users100,000
Groups15,000
Group memberships per user1,500 (20 average)
Spaces5,000
Pages1,000,000
Pages per space10,000
  • 1,000 pages at the same level of hierarchy
  • 20 page hierarchy depth
  • Comments per page100
    Attachments100,000
    Attachments per page1,000 (10 average)
    Global permissions200
    Space permissions200
    Page permissions200
    Application nodes4
    Traffic700,000 HTTP calls per hour

    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:

    • View dashboard
    • View page
    • Create page
    • Edit page (12 collaborators in a single edit session)
    • Add comment
    • Add inline comment
    • Quick search
    • Site search
    • Add attachment
    • View attachment

    Dimensions of a large Jira DC

    A Jira DC with these dimensions is considered large:

    DimensionBaseline
    Issues2,000,000
    Projects2,500
    Users100,000
    Custom fields1,800
    Workflows600
    Groups50,000
    Comments4,000,000
    Permission schemes400
    Issue Security Schemes800
    Attachments660,000
    Agile boards1,450

    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:

    • View dashboard
    • View issue
    • Create issue
    • Edit issue
    • Add comment
    • JQL search
    • Site search
    • Add attachment
    • View attachment

    Dimensions of a large Jira Service Management DC

    A Jira Service Management DC with these dimensions is considered large:

    DimensionBaseline
    Requests1,000,000
    Projects500
    Agents1,000
    Customers20,000
    Custom fields1,000
    Workflows700
    Screens3,000
    Screen schemes500
    Comments2,000,000
    Attachments2,000,000
    Organizations300

    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:

    • View dashboard
    • View request in portal view
    • View request in agents view
    • Create request
    • Edit request
    • Add comment
    • JQL search
    • Site search
    • Add attachment
    • View attachment
    • View queues
    • View reports

    Learn more

    Rate this page: