forks.pm vs. ithreads?

Hi everyone,

Some have been wondering if anyone has used ithreads in a production
application yet.  Well, I have on a fairly hefty application (125+ threads)
on a hefty box (4-cpu linux with 4G physical RAM).  It's working well,
although the memory leak problem is very apparent.  I've ended up restarting
the program once a day to prevent it from dying in an inelegant manner.

Anyway, I'm very interested in Elizabeth's forks.pm module.  I'm wondering
how it compares to ithreads.  I see that forks is much better with memory,
but how about performance?  Besides memory usage, is there any reason to use
one over the other?

And one last question: will Thread::Queue and Thread::Semaphore work with
forks.pm?

Thanks,
-Allen