Hi,

No, with process_msg the program not gows.

I've investigating more an I detect that the problem could be in the get_msg funtion that looks like: 


sub get_msg {


  my $self = shift;


  my ($param) = @_;


  my $consulta_stack = qq{


                         SELECT *


                         FROM out


                         WHERE app = $param


                         ORDER BY id DESC LIMIT 100;


                        };


  my $sth = $self->{dbh}->prepare($consulta_stack);


  $sth->execute();


  my $msgs = $sth->fetchall_hashref('id');


  $sth->finish;


  return $msgs;


}
I also observ that when there's no record in the resultset memory consumption is highter than when there's sontehing.

In reply to Re: Re: Re: Re: Perl memory Memory consumption by alfatux
in thread Perl memory Memory consumption by alfatux

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.