I wondered if index and substr would be any quicker but, no, it came in a bit behind &_split_LIMIT.
use strict;
use warnings;
use Benchmark qw{ cmpthese };
my $string = q{1:13:1:6:5854:0x00E37F06:0x00D1314C};
my $result;
sub _index {
my $pos3 = -1;
$pos3 = index $string, q{:}, $pos3 + 1 for 1 .. 3;
$result = substr $string, 0, $pos3;
}
sub _split {
$result = join ':', (split /:/, $string)[0 .. 2];
}
sub _split_LIMIT {
$result = join ':', (split /:/, $string, 4)[0 .. 2];
}
sub _regex {
($result) = $string =~ m{ \A \d+ : \d+ : \d+ }xmsg;
}
cmpthese(
-5, {
_index => \&_index,
_split => \&_split,
_split_LIMIT => \&_split_LIMIT,
_regex => \&_regex,
}
);
Rate _split _index _split_LIMIT _r
+egex
_split 657900/s -- -26% -31%
+-38%
_index 890097/s 35% -- -7%
+-17%
_split_LIMIT 952857/s 45% 7% --
+-11%
_regex 1066336/s 62% 20% 12%
+ --
I hope this is of interest.
-
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.