[
https://issues.apache.org/jira/browse/TS-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289969#comment-13289969
]
Leif Hedstrom commented on TS-1267:
-----------------------------------
Hmmm. But the issue in client / Origin VCs is not the number of connections,
it's the fact that scheduling gets zucked up when the two NetVCs are on
different scheduler queues. I guess it's completely possible this never causes
latency with the cluster VCs, and if so, just close this as invalid.
> Should we have cache cluster connection pools per EThread ?
> -----------------------------------------------------------
>
> Key: TS-1267
> URL: https://issues.apache.org/jira/browse/TS-1267
> Project: Traffic Server
> Issue Type: New Feature
> Components: Clustering
> Reporter: Leif Hedstrom
> Fix For: 3.3.0
>
>
> Once TS-1222 lands, we might want to look into the possibility of having
> per-EThread cluster connection pools. This assures that the client VC and the
> cluster VC are on the same thread. Similar to how we optimize origin VC
> connections.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
