By breaking each DB handle out to a different core, you could still have idle time (one DB handle consistently takes longer to complete the query, for example).

Can your problem be broken down more at the higher level? In other words, instead of breaking each handle out to a different thread, break the top level data set into N smaller sets and distribute those smaller jobs out to the individual cores. Each core would still have M (4 in this case?) DB handles, but each core could stay busy (less the slight overhead for managing the data sets).

Now, if all of the top-level data is interdependent, then never mind :-)

--MidLifeXis

In reply to Re^3: querying multiple databases in parallel -- attach problem #2 by MidLifeXis
in thread querying multiple databases in parallel -- attach problem #2 by baxy77bax

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.