As previously mentioned, multi-tasking won't help. This prorgram is I/O-bound, and merging the results of the threads would be as expensive as building the results in the first place.

I just wanted to provide a cleaned up version of your code (with a few micro-optimizations). 

#!/usr/bin/perl
use strict;
use warnings;
use feature qw( say );

use Sort::Naturally qw( nsort );

local $/ = '';  # Paragraph mode reads until a blank line.

my %grouped;
while (<>) {
   my @lines = split /\n/, $_;

   for (@lines[1..$#lines]) {
      next if $_ eq '--';   # Omit if rarely true.

      ++$grouped{"D$1"}{$2} while /\bD\*([^*]*)\*([^*]*)\*D\b/g;
   }
}

for my $k (nsort keys %grouped) {
   say "$k=>" . join("|", keys(%{ $grouped{$k} });
}

[download]

In reply to Re: Parallel-processing the code by ikegami
in thread Parallel-processing the code by rajaman

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.