Hello, I am writting a perl script which does few things one after one. Each one is quite big and cpu cost + script will be running every hour. So far I didn't test anything, just wonder if execution of steps described bellow may overload system and what can I do to avoid this. Script steps:
1. open huge text file by: 
open(my $fh, "<", my_file.log")     or  die "cannot open, ($!)\n";

     while (<$fh>) {
     
     chomp;
     next unless $_ =~ /Key/i;

[download]

2. Store "key" lines in hash (may store aprox.1k lines in hash)
3. Analyze stored keys with diffrent values
4.Update Mysql databse

So, what I want to avoid is program crash in the middle of work. Let's say, analyzed text file but didn't update. What can I do ? Maybe ther is a way to slow things a liittle bit (sleep?) and gain stable work ?

In reply to Overload problem by Martin90

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.