AnyEvent-Fork-Pool
view release on metacpan or search on metacpan
A relatively large number of key/value pairs can be specified to influence
the behaviour. They are grouped into the categories "pool management",
"template process" and "rpc parameters".
=over 4
=item Pool Management
The pool consists of a certain number of worker processes. These options
decide how many of these processes exist and when they are started and
stopped.
The worker pool is dynamically resized, according to (perceived :)
load. The minimum size is given by the C<idle> parameter and the maximum
size is given by the C<max> parameter. A new worker is started every
C<start> seconds at most, and an idle worker is stopped at most every
C<stop> second.
You can specify the amount of jobs sent to a worker concurrently using the
C<load> parameter.
You can supply your own template process, or tell
"AnyEvent::Fork::Pool" to create one.
A relatively large number of key/value pairs can be specified to
influence the behaviour. They are grouped into the categories "pool
management", "template process" and "rpc parameters".
Pool Management
The pool consists of a certain number of worker processes. These
options decide how many of these processes exist and when they
are started and stopped.
The worker pool is dynamically resized, according to (perceived
:) load. The minimum size is given by the "idle" parameter and
the maximum size is given by the "max" parameter. A new worker
is started every "start" seconds at most, and an idle worker is
stopped at most every "stop" second.
You can specify the amount of jobs sent to a worker concurrently
using the "load" parameter.
( run in 1.414 second using v1.01-cache-2.11-cpan-de7293f3b23 )