[ 
https://issues.apache.org/jira/browse/TS-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274475#comment-13274475
 ] 

Zhao Yongming commented on TS-1222:
-----------------------------------

first patch that implement multi-tcp connections in cluster, that will give you 
an options for balance the connections between ET_CLUSTER threads, that is more 
cpus you can use, for cluster traffic, IE, you have 10 boxes and each box have 
32+cores.

this patch had been testing for heavy cluster traffic in our testing bed, it 
rocks.

the ongoing task we are working:
1, find out how to balance ET_NET & ET_CLUSTER:
  1.1 should we keep each ET_CLUSTER(thread) one connection to every cluster 
member?
  1.2 why the highest & lowest IP in the cluster have so much diff in CPU 
usage, IE, the ET_CLUSTER in highest IP do not use any CPU, is that a problem 
involved in steal threading?

2, how to deal with pre-cluster content caching?

hopes we can resolve #1 task before V3.2


I need you review for this patch, as it will change the interface we do cluster 
operations, IE, change from ClusterMachine to ClusterHandler, because now 
ClusterHandler:ClusterMachine is now M:1. thanks
                
> single tcp connection will limit the cluster throughput
> -------------------------------------------------------
>
>                 Key: TS-1222
>                 URL: https://issues.apache.org/jira/browse/TS-1222
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Clustering
>    Affects Versions: 3.1.3
>            Reporter: Zhao Yongming
>            Assignee: kuotai
>             Fix For: 3.1.4
>
>         Attachments: cluster.patch
>
>
> kuotai is trying to work around the single tcp performance issue in cluster 
> throughput. hopes we can fix it before 3.2 is out, put it a target for v3.3 
> for now.
> more detail, please take a look at the Clustering in projects on the cwiki.

--
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

        

Reply via email to