Hm. I just tried setting ${^RE_TRIE_MAXBUF} to every power of 2 from 18 through 32 and it didn't make a blind bit of difference. 

...
our $M //= 16; ${^RE_TRIE_MAXBUF} = 2**$M;
...
__END__
C:\test>for /l %i in (18,1,32) do
    @\perl5.18\bin\perl.exe -s 1043602.pl -M=%i C:\docs\OriginOfSpecie
+s(Darwin)\2009-h\2009-h.htm
Finding 203474 words (of 216808) took 0.175862 seconds using a hash
201     Finding 203474 words (of 216808) took 0.174275 seconds using a
+ hash
249     Finding 203474 words (of 216808) took 0.173872 seconds using a
+ hash
174     Finding 203474 words (of 216808) took 0.174906 seconds using a
+ hash
201     Finding 203474 words (of 216808) took 0.175149 seconds using a
+ hash
205     Finding 203474 words (of 216808) took 0.172946 seconds using a
+ hash
183     Finding 203474 words (of 216808) took 0.176250 seconds using a
+ hash
196     Finding 203474 words (of 216808) took 0.175480 seconds using a
+ hash
201     Finding 203474 words (of 216808) took 0.174416 seconds using a
+ hash
196     Finding 203474 words (of 216808) took 0.179129 seconds using a
+ hash
210     Finding 203474 words (of 216808) took 0.174478 seconds using a
+ hash
197     Finding 203474 words (of 216808) took 0.174674 seconds using a
+ hash
183     Finding 203474 words (of 216808) took 0.177501 seconds using a
+ hash
225     Finding 203474 words (of 216808) took 0.174395 seconds using a
+ hash
197     Finding 203474 words (of 216808) took 0.178181 seconds using a
+ hash
221
C:\test>

[download]

Each run was manually killed after checking that the setting made no difference to the memory usage and ~20 seconds had elapsed. As you can see, it was still only processing ~10 line/s.

Personally, I've yet to see a situation where the so-called trie optimisation benefited my code. (See also Re: pattern match, speed problem)

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^3: Efficient matching with accompanying data by BrowserUk
in thread Efficient matching with accompanying data by Endless

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.