Skip to content

test: add test that ensures using the same EndpointIds does not come with a perf hit #3690

@ramfox

Description

@ramfox

We need a test that has:

  • One "server" endpoint that is long-lived
  • One "client" endpoint that continuously dies and restarts with the same endpoint id

And shows that there is no perf hit when the client reconnects, even if the server endpoint still has not cleaned up the previous connection.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions