Ok, thank you for a very detailed and good answer!
To answered my unanswered question first: No, the ordering of data is irrelevant, my thought is that whoever of the subroutines that has data ready should write it immediately, unless another one of them currently writes data. I.e., a queue.

I will benchmark the time it takes to execute the queries in parallell/serial "fashion" to determine if it buys me time.

But for now, I'd be glad to learn how to do this, in case it actually buys me time:-)

I can't go in too much on detail how the fetched data looks. What I can say is that the data contains
1. Product information, such as article number, article description etc, a mix of ID's and text fields, around 10 of each. The number of rows can vary from 10 to 15000, where the last one is more common.

2. A website database. his one holds websites, and can generate c:a 1000 rows.
3. Another website database, with approximately the same specs as number 2.

It feels like "Pass a cloned or (externally) shared XML::Writer object to your threads and (externally) serialise use of it through locking." would be an option. Can you describe how you would do it?

In reply to Re^8: Multithreaded xml writing using XML::Writer by DreamT
in thread Multithreaded xml writing using XML::Writer by DreamT

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.