Re: Server - tasking and long lived connections

[Florian Weimer <fw@deneb.enyo.de>]

Eric Merritt <cyberlync@yahoo.com> writes:

>  Linux threading is a bit less efficient from what I
> understand. I think it by default can handle about 512
> tasks, depending on configuration. This can be changed
> with a custom kernel but even then it starts to get
> inefficient after a certain point.

The 512 tasks limit is probably related to some address space limit,
since each task needs address space for its stack (2 MB by default
with GNU libc pthreads, IIRC).

There are several threading implementations for GNU/Linux (GNU libc,
FSU Threads, GNU Pth, GNU Pth with IBM extensions).  Some of the scale
better than others.

How many parallel connections do you want to handle?  Is data
transferred continuously?  Does your database backend support so many
client connections?

> Using processes never really crossed my mind, I tend
> not to really consider them becuase they have no real
> advantage over threads and alot of disadvantages.

There are advantages.  For example, they are more portable ac