Skip to content

Separate connection pool to backends #3844

@szuecs

Description

@szuecs

During an investigation of a high traffic low latency system we found that access to connection pool in the Go runtime added more than 20ms latency (lock contention in http transport).
We should consider that we can split this by application or route or endpoint.
Likely by route is the simplest but by application the best.
Maybe by endpoint could be a good compromise.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions