Update the agent_connection_timeout workload to show successful throughput on the priority port

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • N&O Prioritized List
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As reported via BF-43852, the upgrade from OpenSSL 3.2 to 3.5 has degraded performance of connections on the priority port during a connection churn scenario. The agent_connection_timeout workload is now showing extremely low throughput for agent connections (via the priority port). We need to update this workload to again provide signal on the efficacy of the priority port. One idea is to introduce/increase the rate limiting of standard connections in the workload and then show that the agent user can still connect.

            Assignee:
            Unassigned
            Reporter:
            Cole Harbeck
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: