comment on

Ok, I'll bite.

You said:

I predict that if instead you read the file sequentially (and advised the operating system that this is what you intend to be doing), the OS will read the data from the file in large gulps and stash it in memory, and it would “lazily” write the output in like manner.

But the OP already said:

I have a reasonably large dataset of html files ( +/- 950K files, average size 23K, total size 21G) which I need to parse ...

So it's not possible to read sequentially.

That said, how much the process can benefit or not from parallelism depends on way too many factors (disk layout, OS, kernel parameters, other workloads on the same infrastructure, the phase of Venus, etc.) It's just not possible to make an absolute statement. As marioroy and Anonymous Monk mentioned above, the OP needs to benchmark it in his particular environment to see how much parallelism is optimal.

In reply to Re^5: MCE: Slow IPC between child and gather process in parent by jeffenstein
in thread MCE: Slow IPC between child and gather process in parent by learnedbyerror

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl-Sensitive Sunglasses
	PerlMonks