my day for benchmarking it seems

#!perl-w



use Benchmark qw(:all);

$toto = 'this+is+my+text';

$count =-5;


$results = timethese($count, 

            {

                'Translating' => sub { my($copy)=$toto; $copy =~tr/+/ 
+/; },

                'Substituting' => sub { my($copy)=$toto;$copy =~s/\+/ 
+/g; },

            },

            'none'

        );

        cmpthese( $results ) ;

__END__

Yielded:

                 Rate Substituting  Translating
Substituting 140156/s           --         -68%
Translating  436379/s         211%           --

[download]

Another perl function which out performs regex is index(), for checking for exact matches in textual data: 

#!perl-w

use Benchmark qw(:all);

$toto = 'this+is+my+text';

$count =-5;


$results = timethese($count, 

            {

                'Indexing' => sub { my($copy)=$toto; $index = index($c
+opy, 'is');},

                'matching' => sub { my($copy)=$toto;$match if $copy =~
+/is/; },

            },

            'none'

        );

        cmpthese( $results ) ;

__END__
Gave:
             Rate matching Indexing
matching 552818/s       --     -14%
Indexing 641382/s      16%       --

[download]

but obviously there are limitations, with tr// you can't use it on only part of a string and index() only returns the position of the first match of an exact term or character in text data. The extra control and options offered by regex are what make them slower than both these functions in given situations.

Update

As Davido pointed out the original benchmark tests were flawed and have since been adjusted.

You spend twenty years learning the spell that makes nude virgins appear in your bedroom, and then you're so poisoned by quicksilver fumes and half-blind from reading old grimoires that you can't remember what happens next.

In reply to Re: Difference between tr// and s///? by Sol-Invictus
in thread Difference between tr/// and s///? by kalamiti

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.