For completeness, here's the code using Parallel::ForkManager. Calling MCE::Shared->init() is important to spread out IPC across 12 data channels. Not doing so, means all 200 workers share a single data channel and take much longer to run. Init is called automatically for MCE, MCE::Hobo and threads.
Parallel::ForkManager
use strict;
use warnings;
use Parallel::ForkManager;
use MCE::Shared;
use Time::HiRes 'time';
my $n = MCE::Shared->scalar(0);
my $s = time;
my $fork_manager = new Parallel::ForkManager(200);
$fork_manager->set_waitpid_blocking_sleep(0);
foreach my $child ( 1 .. 200 ) {
my $pid = $fork_manager->start($child) and next;
# init optionally takes an integer value
MCE::Shared->init($child);
my $v; $v = $n->incr() for 1 .. 933;
$fork_manager->finish($child);
}
$fork_manager->wait_all_children;
printf "duration: %0.3f\n", time - $s;
print $n->get(), "\n";
__END__
main process, shared-manager process, and 200 workers
Parallel::ForkManager: ~ 1200K per worker
It's great knowing that MCE::Hobo isn't far behind regarding memory consumption. What I've learn is that simply loading modules doesn't tell the whole story. One must capture memory consumption while running for a better picture. :)
Regards, Mario
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|