On Thu, Feb 6, 2014 at 7:09 AM, Goswin von Brederlow <[email protected]>wrote:
> On Thu, Feb 06, 2014 at 01:38:48PM +0100, Olaf Mandel wrote: > > Hello, > > > > But what if you don't use threads? Then inproc won't work. But also > you don't have a limit of 1024 sockets. Only 1024 file descriptors per > executable. By forking or starting seperate executables you can have > many more sockets, colletively. How much more? There are only 65536 > ports and 0-1023 is reserved for root. So you won't get verry far with > tcp. It's true a client can only make ~60K outgoing connections (due to ephemeral port exhaustion) but a server with bound sockets can have up to 64K connections _per port_. Here's a blog post from urban airship detailing their experiments with pushing connection limits up to 500K on a single machine: http://urbanairship.com/blog/2010/08/24/c500k-in-action-at-urban-airship/ -Michel > If you need more then you need to use multiple hosts or at least > containers with different IPs. > > Or use unix domain sockets so you are not limited by the number of > ports for tcp. > > MfG > Goswin > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
