The OP said he was successful in splitting his huge file and putting each chunk into a thread for processing, but was unsure on how to collect the output generated by each thread. He said a database write was unacceptable to his boss.
The concept of each thread writing to it's own output file and merging them after script completion didn't appear a good solution to him, or else he wouldn't have brought the issue up.
Consider a situation where the threads process millions of records, but only need to report back a few matches. This method will allow the main thread to collect those matches, and operate on them in realtime. Otherwise the main thread would have to tail the thread's output files.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.