Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-2195

Testing performance and stage pipelines for system stability

    XMLWordPrintable

Details

    • Beta perf/testing
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • 100
    • 100% 100%
    • Approved

    Description

      The Hub codebase of galaxy_ng plus ansible-hub-ui are typically used with a relatively lower volume of data. Today on beta-galaxy.ansible.com this codebase exists with the high volume of data migrated from galaxy.ansible.com. We currently have bugs associated with higher variety of data that hit corner cases, and higher volume of data.

      We also need to ensure stability with a high volume of traffic that galaxy.ansible.com regularly experiences. As noted in AAH-2047 comment we are experiencing a year over year doubling of traffic, currently at an average of 6,013 requests/minute, peak 15,924 requests/minute.

      Acceptance Criteria:

      • we have pipelines setup for Beta galaxy (similar to CRC)
      • need criteria about performance (work with perf and scale team?)

       

      notes on perf testing:

      • to sufficiently test perf in beta galaxy, need a lot of IP addresses to run clients, and scale it
      • we're going to hit performance issues from a single machine if we get rate limited, so need to test from multiple incoming IP addressses

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. AAH-2229 Unable to sync against beta unless 10 at a time

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. AAH-2332 Concurrency bugs in repo management with many parallel collection publishes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          split to

          Bug - A problem that impairs or prevents the functions of the product. AAH-2143 Investigate beta-galaxy.ansible.com 502s

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. AAH-2204 Recursive redirects on download endpoint

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              drodowic@redhat.com Daniel Rodowicz
              awcrosby5 Andrew Crosby (Inactive)
              Apurva Bakshi Apurva Bakshi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: