Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

Re^2: Special case mktime: semi-sequential access

by Dallaylaen (Friar)
on Jul 01, 2013 at 10:58 UTC ( #1041815=note: print w/replies, xml ) Need Help??


in reply to Re: Special case mktime: semi-sequential access
in thread Special case mktime: semi-sequential access

To me it looks like a multiplication by 60 is simple enough and doesn't deserve caching. On the other hand, calculating date is tricky as it involves legacy code dating back to the Roman empire. So the OP approach definitely has some grounds. I wonder what benchmark would say though.

Besides, a log file is not always sequential if several applications run at once and buffering is involved.

  • Comment on Re^2: Special case mktime: semi-sequential access

Replies are listed 'Best First'.
Re^3: Special case mktime: semi-sequential access
by not_japh (Novice) on Jul 01, 2013 at 11:48 UTC
    Sequential not necessary. Just within the same day is enough to avoid the date calculations by doing the time ones yourself.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1041815]
help
Chatterbox?
[stevieb]: berrybrew has been updated with the new perl checksums. Now I'm going to implement dynamic loading of perls thanks to their new JSON releases file
[LanX]: GotToBTru ++ # erix & MySql ... talk about a database trigger xD

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (12)
As of 2017-03-30 16:01 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Should Pluto Get Its Planethood Back?



    Results (360 votes). Check out past polls.