You are correct, I have used the module just as described in the referenced node. I'm planning on writing up a synopsis of what I had to do, how I did it, and how it all works and stick it under craft.
However, since you asked here's a short answer. I did use Parallel::ForkManager to solve my problem, I followed the following suggestions from the thread:
- I uncompressed each file to a temporary location (not /tmp) and then deleted it after the reformatting was through.
- I made sure that the temporary location was on a different physical drive from the permanent location for the formatted files.
- I rewrote my program to divide the work into 4 distinct sets, and then forked a process for each set.
- I switched to the GNU version of gzip because of this reply (the GNU version is supposedly faster).
- I staggered the initiation of the threads by sleeping for 60 seconds to try and avoid competition for disk I/O.
There's a bit more about the optimization that I've done, but look for it under Craft in the next few weeks.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||