jettero,
Time::Local does some internal caching so subsequent lookups in the same month should be really fast assuming your dates are all being parsed within the same instance of the interpreter. So then it is a matter of speeding things up as fast as possible: 
# Keep the lookup table in highest scope necessary to avoid create/des
+troy each time needed
my %lookup = ( Jan => 0, Feb => 1, ... );

#Assume unpack is faster than regex (Benchmark.pm to be sure)
# Add code to handle year appropriately
my ($mon, $day, $hr, $min, $sec) = unpack('A3xA2xA2xA2xA2', $date);
$mon = $lookup{$mon};
my $stamp = timelocal( ... );

[download]
Sorry this is just an outline, I am off to the aiport and had to hurry.

Cheers - L~R

In reply to Re: Fast date parsing by Limbic~Region
in thread Fast date parsing by jettero

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.