Okay. I guess I didn't read the POE example closely enough and was assuming a 'normal' POE event driven, single process approach--and it does actually mention forking at the top.

That said, it would be an interesting exercise to see how much calculation the asynced sub would have to be doing in order to offset the overhead of spawning (two?) new processes and all the IPC etc. before it would show benefit over just calling them serially. I would imagine the breakeven point would be pretty high.

That said, this application isn't really what POE is designed for. I think POE is very clever--just rather complex. Going by the list of around 400 POE related modules on CPAN, it seems as if every new problem requires a unique solution tailored to that specific problem? Even then, the applications using those modules hardly seem simple, and the use of POE is far from transparent. Threads just seem easier to use to me :)

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^3: My First POE - Simple Parallel Programming by BrowserUk
in thread My First POE - Simple Parallel Programming by monkfan

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.