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