comment on

You might want to also try using a file handle opened on a reference to your string:

    filehandle => sub {
        my @lines;
        open my $str_fh, "<", \$str or die "cannot open fh $!";
        while (<$str_fh>) {
            chomp;
            s/o/i/g;
            push @lines, $_;            
        }
    },
[download]

This appears to be faster than your other subs, including the one with split (note that I had to change the count value for the result to be meaningful):

$ perl bench_split.pl
           s/iter      regex      index      split filehandle
regex        3.44         --        -9%       -36%       -48%
index        3.13        10%         --       -29%       -43%
split        2.21        56%        42%         --       -19%
filehandle   1.78        93%        76%        24%         --
[download]

In reply to Re: Is foreach split Optimized? by Laurent_R
in thread Is foreach split Optimized? (Update: No.) by haukex

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks