RE: RE (tilly) 2: When is a while not a while?

[jreades]

What are the tradeoffs between fork() and threads?

As I said, I've only used threads in Java (which AFAIK has no forking) and they are one of the fundamental classes... Anyway, tradeoffs: discuss.

TIA

[merlyn]

Well, as a first approximation:"fork" works, "threads" don't. {grin}

-- Randal L. Schwartz, Perl hacker

[tilly]

This is a complex subject, but you got me in a good mood. :-)

A full response may be found at Threads vs Forking (Java vs Perl).

[jreades]

Well, you supplied a great explanation (particularly in combination with the geeksalad article) -- I now know just enough to be dangerous. :^P

Let me see if I understood what was written and can apply it to the problem at hand...

We need one application/process/thread ('a') to instantiate/launch/spawn another ('b') that will perform function 'x' while 'a' waits for keyboard input...

Under Unix/Perl, this would be an exec situation as we don't need 'a' to clone itself, but we *do* need it to launch 'b' as a distinct process.

Now there are two possibilities, depending on whether or not 'a' and 'b' need to communicate after the exec().

If they do not -- i.e. that 'b' will run until it has done 'x' and then exit.

But if 'a' and 'b' still need a way to communicate, then we need to avoid trampling all over the shared information (a 'race condition'). One way of avoiding this is supplied by tilly as SimpleLock, and I think that this LockFile-Simple might also allow the processes to pass information back and forth.

Am I on the right track?

[tilly]

In Unix when you fork you usually wind up communicating between the processes in a pipe. With threads the two can communicate directly through an internal buffer (they share the same memory). With Unix you don't have to worry about how you use data, but there is more overhead. With threads you do have to be careful because the threads can trample over each other, but you can get better performance.

Where locking is necessary is when two things (threads, processes, machines in a cluster, whatever) need to synchronize access to the same resource. Think here of Highlander - allow only one invocation at a time of an expensive CGI script, or also think of some CGI script that updates some user file. If your user submits twice you now have 2 processes, one of which might be reading while the other is deleting...

That is a race condition. If the first cleanly read, rewrote, and exited, you would be fine. The second likewise. If they collide...

It just happens to be really easy for two threads to collide. And much less common for programs to do it.