Ofcourse!
In short I've been performing some simple experiments to get a feel for how
sockets and libev work.
- First: I've tried to open 10K sockets simultaneously. This was for me the
simplest way to verify that the kernel allows me to do that. During this
process I found that this is only
Hi Marc, Hi Gabriel,
Thank you for the replies! This is super helpful for me. My ulimit is high
enough and I do check for errors, I haven't looked at the loop speed and
the listen queue length. I will definitely look into those. I'm on Ubuntu
by the way.
Is it valuable for this email list if I
Hi Marc, Hi Gabriel,
Thanks again for the replies! After experimenting a bit more, based on your
directions, all turned out fine and I now have C15K! Libev is awesome!
Best,
Marcel
___
libev mailing list
libev@lists.schmorp.de
On Tue, Aug 28, 2012 at 4:23 PM, Marcel Wijnen mmfwwij...@gmail.com wrote:
Thanks again for the replies! After experimenting a bit more, based on
your directions, all turned out fine and I now have C15K! Libev is awesome!
For posterity, can you possibly give a short post-mortem of your
On Mon, Aug 27, 2012 at 06:59:39AM +0200, Marc Lehmann wrote:
d) is your listen queue long enough?
On Linux, remember that the listen queue lenght is limited by the kernel
parameter net.core.somaxconn (to 128 by default). You need to increase it
before you call listen (hence restart your
Hi All,
Currently I'm starting to getting to know Libev. Thanks to anyone who
contributed to this library.
Just as an experiment I've set up a simple listening socket that accepts
connections. My goal is to accept about 10K connections. After accepting
the connections nothing is done. The point
On Sun, Aug 26, 2012 at 10:06:03PM +0200, Marcel Wijnen mmfwwij...@gmail.com
wrote:
connections can be accepted at once. Out of 10K connections typically a
couple of hundred are dropped.
Well, it's not really related to libev, but here are a few things to check:
a) ulimit -n
b) do you run
