But any logic that expects "compute" cores to have to do I/O whether database or otherwise is quickly going to find all those "parallel" engines ... serialized. Working one-at-a-time or nearly so in a work flow that can actually be considerably slower than having ... one process. You will need to design more infrastructure here than either MCE or MCE::Shared is by itself really intended to provide, to feed the now-truly- compute cluster with data without delaying them, and also disposing of the computed data also without delay. While your example is interesting, it simply would not scale.
-
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.
|
