[erlang-questions] stress test with tcp_server

[Francesco Cesarini]

Have a look at the ulimit flag to increase the 1024 limit (Some other 
application must be hogging the remaining 8).

Oscar's thesis on maximising TCP/IP connectivity (and simultaneously 
open connections) in Erlang based systems might also be of interest. You 
can read it here:

http://www.erlang-consulting.com/thesis/tcp_optimisation/tcp_optimisation.html 
and
http://www.erlang-consulting.com/thesis/tcp_optimisation/tcp_optimisation_slides.html

Regards,
Francesco
--
http://www.erlang-consulting.com


Adam Lindberg wrote:
> Ah, of course. My bad. :-)
>
> Then Gaspar's tip is correct, perhaps together with multiple computers.
>
> Cheers!
> Adam
>
> On 6/25/07, Jeremy Chow <erlanging@REDACTED> wrote:
>   
>>> I would try to close the sockets in between, or reuse them (for example by creating a socket pool). Because, in your loop, you create a lot of sockets but never close them.
>>>
>>>       
>> My original intention is to test how many active connections the
>> server can accepted, so I donot close the socket advisedly.
>>
>>     
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>
>
>