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.
-
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.
|