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

Determine sync performance next steps

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Task Task
    • Resolution: Obsolete
    • Icon: Normal Normal
    • None
    • None
    • QE
    • None
    • False
    • False
    • None

      Both Epic AAH-534 “Use v3/excludes/ with sync”  and Epic AAH-306 “Use unpaginated streamed v3/collections/all with sync” make performance improvements to sync.

      The v3/excludes endpoint may be the highest priority since in addition to sync performance improvements, it has potential to greatly increase the stability of the cloud installation by reducing the high number of tasks created for each synclist repository when collections are added, deleted, or toggled.

      • Determine if Epic AAH-306 v3/collections/all is a pre-req of Epic AAH-534 v3/excludes/
      • In thinking about whether we need to do AAH-306 v3/collections/all, we may want to test the sync performance against c.rh.c after we release 'Cloud Catch up release' since other performance improvements may lower the need for that
      • In thinking about if/when to do AAH-306, see AAH-1013
      • Adjust priority of AAH-534 v3/excludes/ and agree when to work it 

              cspealma@redhat.com Clara Spealman (Inactive)
              hesmith@redhat.com Heather Smith
              Archiver:
              ranumula@redhat.com Raju Anumula

                Created:
                Updated:
                Resolved:
                Archived: