What it more efficient fork or thread?

ruby-talk
1

Hi !

I will write a small TCPServersystem and my question is, what is more
efficient for that, always start a Childprocess if there is a new connenction
request or should i only start a new thread . And what is easier to handle ?

mfg. Jonas Hoffmann

2

For a small server the threaded model is IMO both more eficient and easier
to handle. The skeleton for the threaded TCP server is just a few lines of
Ruby code.

In general - it depends. For example you can not run different threads on
different CPUs which is possible with different processes.

Regards,

Dalibor Sramek

···

On Mon, Jan 06, 2003 at 03:30:25PM +0900, Jonas Hoffmann wrote:

I will write a small TCPServersystem and my question is, what is more
efficient for that, always start a Childprocess if there is a new connenction
request or should i only start a new thread . And what is easier to handle ?

–
Dalibor Sramek insula.cz | In the eyes of cats,
dalibor.sramek@insula.cz | all things belong to cats.

3

Thanks.
By the moment i have only a OneCPU Machine :frowning:

mfg. Jonas Hoffmann

···

Am Montag, 6. Januar 2003 07:44 schrieb Dalibor Sramek:

In general - it depends. For example you can not run different threads on
different CPUs which is possible with different processes.

Regards,

Dalibor Sramek