Why not create three worker threads. Whenever a new file arrives, add it to the queue. The workers pick stuff off the queue as they become idle. 
use strict;
use warnings;

use threads;
use Thread::Queue qw( );

my $num_workers = 3;

sub process_file {
   my ($file) = @_;
   ...
}

my $q = Thread::Queue->new();

for (1..$num_workers) {
   async {
      while (defined(my $file = $q->dequeue())) {
         process_file($file);
      }
   };   
}

for (;;) {
   ... wait for new files ...
   $q->enqueue(@new_files);
}

$q->enqueue() for 1..$num_workers;
$_->join() for threads->list();

[download]

Adding use forks; should make the above use processes instead of threads.

In reply to Re: read directory, fork processes by ikegami
in thread read directory, fork processes by KevinBr

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.