Well, my name's in the title, I have to respond, right? :)

Are you sure that's 5.6? I was playing around with that when I saw your post on the beginner's list. I've gotten the following:

    cmpthese(-3, {
      cc => sub { 'asdfasdfXasdfasdfXsdfasdfXasdfasdf111XYZ' =~ /(?:[^
+X]*X)+?YZ/  },
      ds => sub { 'asdfasdfXasdfasdfXsdfasdfXasdfasdf111XYZ' =~ /.*?XY
+Z/  },
    });
[download]

Results:

    Benchmark: running cc, ds, each for at least 3 CPU seconds...
            cc:  4 wallclock secs ( 3.12 usr +  0.00 sys =  3.12 CPU) 
+@ 101652.97/s (n=316649)
            ds:  4 wallclock secs ( 3.12 usr +  0.00 sys =  3.12 CPU) 
+@ 243115.24/s (n=759492)
           Rate   cc   ds
    cc 101653/s   -- -58%
    ds 243115/s 139%   --
[download]

And the version:

    C:\>perl -v
    This is perl, v5.6.0 built for MSWin32-x86-multi-thread
    (with 1 registered patch, see perl -V for more detail)

    Copyright 1987-2000, Larry Wall

    Binary build 620 provided by ActiveState Tool Corp.         http:/
+/www.ActiveState.com
    Built 18:31:05 Oct 31 2000
[download]

Update: I upgraded to 5.6.1, build 629 and am getting similar results:

    Benchmark: running cc, ds, each for at least 3 CPU seconds...
            cc:  3 wallclock secs ( 3.19 usr +  0.01 sys =  3.20 CPU) 
+@ 116044.62/s (n=371923)
            ds:  3 wallclock secs ( 3.13 usr +  0.00 sys =  3.13 CPU) 
+@ 250170.39/s (n=784034)
           Rate   cc   ds
    cc 116045/s   -- -54%
    ds 250170/s 116%   --
[download]

Just to be safe, I used your exact cmpthese code above:

    Benchmark: running cc, ds, each for at least 3 CPU seconds...
            cc:  2 wallclock secs ( 3.08 usr +  0.01 sys =  3.09 CPU) 
+@ 319288.07/s (n=987558)
            ds:  3 wallclock secs ( 3.19 usr + -0.01 sys =  3.18 CPU) 
+@ 292251.18/s (n=930820)
           Rate  ds  cc
    ds 292251/s  -- -8%
    cc 319288/s  9%  --
[download]

After running it several times to get consistent results, I see that the optimization still seems to be dependant on the text one is matching against. Am I just missing something obvious here? Do the 'non-capturing' parens throw it off? My original code comes from your reply on the beginner's list.

Cheers,
Ovid

P.S.: if you're one of the three Perlmonks who doesn't "get" the reference in japhy's title, see Death to Dot Star!

Vote for paco!

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.