Without any details, it is hard to tell. Super Search for thread fork revealed a recent thread When to use forks, when to use threads ...? that might already provides some helpful answers for you? If not, please tell us a little bit more about the details.

I have read the URL you pointed out, thanks for providing the useful link, I should have used super search.

There's a lot of guff and bluster around on this subject. And a lot of it comes from otherwise rational and reliable sources.

I needed a quick "concurrent clients" socket server for testing another piece of code against, so I knocked this up:

#! perl -slw
use strict;
use IO::Socket;
use threads;

our $ADDR ||= 'localhost:35007';

my $listener = IO::Socket::INET->new(
    LocalAddr => $ADDR,
    Listen => 5,
    Reuse   => 1,
) or die $^E;

while( my $client = $listener->accept ) {
    async {
        my($port, $iaddr) = sockaddr_in( getpeername( $client ) );
        printf "From %s:%d: %s", join('.',unpack 'C4', $iaddr ), $port
+, $_
            while <$client>;
        close $client;
    }->detach;
}
[download]

Simplistic, but it easily keeps up with 5 of these each fowarding the traffic from 100 monitored log files, so it didn't need to be any more complex.