Uploaded image for project: 'OpenShift Image Registry'
  1. OpenShift Image Registry
  2. IR-121

R&D Benchmarking tool for registries

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • Other

      User Story

      As a developer of OpenShift Image Registry
      I want to stress test the registry
      So that I can identify bottlenecks

      Acceptance Criteria

      • List of workload types that we are interested to use for performance testing (N users - M repos - K actions (push/pull) - L images)
      • List of metrics that we care about (response time, memory usage, ...?)
      • What images should it use? Should it use pre-built images?
      • How to scale it?
      • How to deploy it? (the same k8s cluster?)
      • Should it be able to test a single endpoint (for example, /openshift/token or /v2/REPO/NAME/blobs/...)?

      Launch Checklist

      Dependencies identified
      Blockers noted and expected delivery timelines set
      Design is implementable
      Acceptance criteria agreed upon
      Story estimated

      Notes

      Scripts that are used by Quay team: https://github.com/quay/quay-performance-scripts

              ngutu@redhat.com Nichita Gutu (Inactive)
              obulatov@redhat.com Oleg Bulatov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: