Algorithms should scale quite differently to this. Char based solutions (bit ops, tr) would not profit. String / regexp based solutions like index, s//, split could gain speed. I'm not a regexp engine guru, but I assume the engine is intelligent enough not to compare char with char in this situation. In the most common case you get away with comparing the 1st char of the search string with every 3rd char of the long "text" string. That's a 3-fold speed increase.

Thanks to very experienced monks the regexp engine is not too bad in real world use cases.

Edit: Even index takes more than one char.

In reply to Re^4: Challenge: CPU-optimized byte-wise or-equals (for a meter of beer) by NiJo
in thread Challenge: CPU-optimized byte-wise or-equals (for a meter of beer) by dragonchild

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.