MySQL 4.1.13-debian + large HEAP table
am 05.08.2005 22:43:21 von gaga moo
I've been running mysql with the exact same
configuration for a while now, I have a heap table
150K rows which is a mirror of a disk table.
On a normal basis mysql used to consume about 300MB of
resident and 300MB virtual. Things have been running
stable for a long time now and mysql's memory
consumption has been slowly increasing due to new data
being added to the heap table on a regular basis.
Now all of a sudden mysql surges in memory consumption
from the normal figures to more than double and triple
within minutes.
Something I do must trigger a major leak somewhere, I
would appreciate anyone's help on how to debug this
issue and how to find where most of this memory is
being consumed.
Thanks a lot
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org
Re: MySQL 4.1.13-debian + large HEAP table
am 07.08.2005 04:28:49 von miguel solorzano
At 17:43 5/8/2005, gaga moo wrote:
Mr Gaga,
Could you please if you a repeatable test case for the behavior reported
use our Bug Database System at:
http://bugs.mysql.com/
Where you will find instructions how to report bugs.
Thanks in advance.
Regards,
Miguel Angel Sol=F3rzano
Florianopolis Santa Catarina - Brazil
--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=3Dgcdmb-bugs@m.gmane.org
Re: MySQL 4.1.13-debian + large HEAP table
am 08.08.2005 14:19:39 von gaga moo
Miguel,
MySQL in my case is the backbone of a fairly complex
web application, so far things have been stable but
very recently mysql started acting up. This is
probably due to changes in the site.
But in order to make a reproducable test case and
submit a bug (if indeed it's a bug in mysql) I would
need to know how to pinpoint the issue and find out
for myself and you how to reproduce this.
Please give me some pointers on how to see exactly how
mysql is using all that memory when it starts eating
all my system memory up ...
I will leave a script running in the background that
once in every few minutes checks mysql's memory usage
and will execute any set of queries and log them for
me whenever this happens again (as well as
automatically restart mysqld for me, after the queries
have been executed).
Thanks a lot!
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org
Re: MySQL 4.1.13-debian + large HEAP table
am 08.08.2005 18:01:23 von Sergei Golubchik
Hi!
On Aug 08, gaga moo wrote:
> Miguel,
>
> MySQL in my case is the backbone of a fairly complex
> web application, so far things have been stable but
> very recently mysql started acting up. This is
> probably due to changes in the site.
Do you mean it was not due to MySQL upgrade ?
> But in order to make a reproducable test case and
> submit a bug (if indeed it's a bug in mysql) I would
> need to know how to pinpoint the issue and find out
> for myself and you how to reproduce this.
>
> Please give me some pointers on how to see exactly how
> mysql is using all that memory when it starts eating
> all my system memory up ...
"exactly" is problematic :(
but some hints are still available:
> I will leave a script running in the background that
> once in every few minutes checks mysql's memory usage
> and will execute any set of queries and log them for
> me whenever this happens again (as well as
> automatically restart mysqld for me, after the queries
> have been executed).
Try usual commands SHOW VARIABLES; SHOW STATUS;
SHOW INNODB STATUS, if you use InnoDB.
And also 'mysqladmin debug'.
Ah, by the way, if you have debug build of mysqld (with safemalloc),
then 'mysqladmin debug' will list ALL the memory allocations - looks
like "exactly" what you were asking for :)
Regards,
Sergei
--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Kerpen, Germany
<___/ www.mysql.com
--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org