When you're doing encryption you will be hitting CPU limits. The work will happen in the background I/O thread, not your application thread. So start as many I/O threads as you have CPU cores. How you match sockets to application threads is going to be insignificant.
On Thu, Feb 13, 2014 at 6:08 PM, Laurent Alebarde <l.aleba...@free.fr> wrote: > Hi all, > > In a server, I want to assign one socket per client (CURVE). What is the > best in terms of performance & ressources ? Say I want to deal with 1,000 > simultaneous clients. > > one socket per thread with an avarage cpu load <1%, and 1,000 threads ? > 100 sockets per thread with an avarage cpu load near 100%, and 10 threads ? > anything between ? > > Some service delivery latency is acceptable. > > > Laurent > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
