Thanks to respond so soon. we assumes that with the option named -n it´s create #cpus worker threads . If not specified, named will try to determine the number of CPUs present and create one thread per CPU.
If it is unable to determine the number of CPUs, a single worker thread will be created. In our case, we dont put -n parameter, and bind up 35 threads, (32 = 32 CPU and other three that whe dont know). I like to know if it,s possible up more than one process per CPU.We have these two machines configured with an only physical interface and at the moment they are serving 2000 qps of real trafic. Few days ago we configured the load balancer to send it about 4000 qps and we saw the same case that you many clients queries timed out/were dropped. We also thought that with more interfaces we increase the yield of the machine because we have one machine with two interfaces and a good yield, ¿we dont know why?. But it is something that we have still not proven in the T2000. I read in the post something like “BIND put more threads in recvmsg”, could you explain me that, please, or tell me where can i read some about this. Thanks for everything. This message posted from opensolaris.org _______________________________________________ networking-discuss mailing list [email protected]
