On Fri, Oct 20, 2006 at 04:17:52PM +0800, ke han wrote:
> Thanks for the reply.
> This app is intended to keep 20,000++ sockets alive at a time. These
> sockets are very long lived.
> I understand about kqueue. I will eventually write for this.
> What I need to understand are the various kernel
Thanks for the reply.
This app is intended to keep 20,000++ sockets alive at a time. These
sockets are very long lived.
I understand about kqueue. I will eventually write for this.
What I need to understand are the various kernel tunings required to
handle 20,000++ active sockets. I would
On Thu, Oct 19, 2006 at 11:24:30PM +0800, ke han wrote:
> I am writing a socket server deamon in C++ on FreeBSD 6.1 (or 6.2 if
> this matters to your answer). What this does is accept many sockets
> and does a little work with each. Each socket has low traffic but
> stay connected for long
On Oct 19, 2006, at 8:24 AM, ke han wrote:
So my desire is two things:
1 - good event handling for knowing which sockets have new data. I
assume kqueue is the way to go here?
kqueue would be a fine choice, otherwise the typical mechanism
involves using select().
2 - I need to know what m
I am writing a socket server deamon in C++ on FreeBSD 6.1 (or 6.2 if
this matters to your answer). What this does is accept many sockets
and does a little work with each. Each socket has low traffic but
stay connected for long periods. All these sockets get accepted
through one public ip