Good day, monks.
I've seen some of the old discussion threads about the virtues/short-comings of perl's implementation of ithreads, and was wondering if changes released since most of these discussions (late '03) have converted any of the fork devotees.
To summarize what I got out of earlier talks, my impression was that perl's non-COW address space copying with ithreads made them actually "heavier" than the optimized fork() routines on most *nix systems. Data sharing was more convenient, but otherwise ithreads seemed to be frowned upon. Liz's forks.pm package, which implements the threads.pm interface using forks and sockets, seemed the more popular approach.
Now, admittedly, looking at the release notes, it seems like all we've really gotten is memory leak fixes for ithreads, not performance help. Nevertheless, when I run the same code with "use threads" vs "use forks", I get better perf with threads, regardless of any sharing. I'm still working on getting reliable cpu time numbers (it's tough to track child processes), but wall clock time on the same system is consistently faster for threads, and threads get 1/4 the page faults (more or less).
Does this seem consistent with what others would expect? Thanks.