envoyproxy/envoy
GitHub で見るseparate ConnectionPool from Cluster definition, make it sharable across Envoy worker threads
Open
#11,071 opened on 2020年5月5日
area/httparea/perfhelp wanted
Repository metrics
- Stars
- (27,997 stars)
- PR merge metrics
- (平均マージ 8d) (30d で 378 merged PRs)
説明
sometimes we deploy multiple services among a set of endpoints, we define a set of clusters on these machines, each has a pool connecting to the same set of endpoints.
Separating ConnectionPool from Cluster has many advantages:
- The same set of backends may be used to serve multiple services, they can share the same connections, better performance, less RAM footprint, less pool warming.
- different LB algorithms on same set of connections,
- possibly introduce context awareness between services/clusters when their backends are the same.