• Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • Sippy Performance & Scalability
    • False
    • None
    • False
    • Not Selected
    • In Progress
    • 33% To Do, 33% In Progress, 33% Done

      As more releases, jobs and tests are brought into classic sippy our usage of Postgres is getting harder to update and maintain.

      Devan has noted our current DB Instance CPU is regularly pegged at 100%
      Our materialized view refreshes can take over an hour at times
      We don't feel that we can continue to scale with the current architecture

      This epic is to coordinate current design limitations and to design and implement more scalable solution

              Unassigned Unassigned
              rh-ee-fbabcock Forrest Babcock
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: