So you've used the referenced module, forks ? Your use of the plural and my expectations both lead me to suspect that you misunderstood the node you replied to and didn't follow the offered link.
On a platform with real fork support, I'd expect the technique outlined in forks to be more memory efficient and, at least in some respects, faster than Perl threads (and not terribly slower in any respect), and perhaps less buggy. Note that this has everything to do with how poorly Perl's particular implementation of threading is, not a problem with threading in general.
Now, trying to use this module on Win32 would just be silly (unless using cygwin Perl). It'd be using fork which Perl turns into a bad emulation of fork(2) using a bad implementation of threads and then the module uses some IPC (which Perl might also be emulating) on top for sharing variables. So emulating Perl's bad threads by using a badly emulated fork that still uses Perl's bad threads. Yeah, I'd expect that to be awful. So that's another possible explanation for your reaction.
- tye
In reply to Re^6: Multi-thread database script (forks.pm)
by tye
in thread Multi-thread database script
by nandn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |