Uploaded image for project: 'OpenStack Strategy'
  1. OpenStack Strategy
  2. RHOSSTRAT-576

Forwarding Performance Benchmarking for Amphora VM / LB

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Octavia LBaaS
    • None
    • Important
    • Not Selected
    • False
    • False
    • Hide

      None

      Show
      None
    • 0
    • 0
    • Red Hat OpenStack Services on OpenShift (formerly Red Hat OpenStack Platform)

      Feature Overview 

      Customers often want to understand how the forwarding performance of Octavia LB compares with other load balancers available (commercial and open-source). Additionally, customers would like to understand how to dimension the Amphora VMs in terms of CPU and memory to achieve the target forwarding performance. Currently, we do not have reliable forwarding performance benchmark numbers to provide accurate guidance or assess the upper limit for the amphora VM forwarding performance.

      Goals

      This feature is applicable to all the customers who want to deploy Octavia for loadbalancing services. Objective is to have reliable performance benchmarking data that can be used to provide customer guidance for dimensioning and assessing the scale requirements.

      Requirements 

      Performance Metrics: Bandwidth (pps), requests/sec, max concurrent connections, connections/sec/ latency

      Traffic Type: HTTP, TCP, UDP

      Frame size: 62 bytes, 256 bytes, 1024 bytes

      Performance measurement with TLS enabled/disabled

       

      Requirement Notes isMVP?
           
           

       

      Done - Acceptance Criteria 

      Performance benchmarking report for the given performance metrics and traffic mix and criterias

       

      Documentation Considerations 

      Performance benchmarking report. The report is intended for internal purpose and not to be published on the customer portal.

       

       

      Team Sign Off (Completion while in Planning status)

      • All required Epics (known at the time) are linked to the this Feature
      • All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
      • Add - Reviewers name, Team Name
      • Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
      • Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone
      Reviewed By Team Name Accepted Notes
             
             
             
             

       

              tfreger Toni Freger
              rh-ee-gurpsing Gurpreet Singh
              Gurpreet Singh Gurpreet Singh
              rhos-dfg-networking-squad-vans
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: