Hi!
If InnoDB only used 600 MB, but the total mysqld process size was 1.2 GB, then the MyISAM/sorting usage should have been 600 MB. Could this be possible due to sorting in many concurrent connections? 16 connections is not much.
You should lower the MyISAM key buffer size even more, and monitor SHOW PROCESSLIST.
If we do not find an explanation, this may be a memory leak on the MySQL side.
Regards,
Heikki
........
Reposting this from the news group:
Eddie,
oops, I did not notice this:
>> Top shows mysql steadily consuming more resourses over a period of 2
>> hours, up to 1.2 Gb, before it crashes.
Please monitor also SHOW PROCESSLIST. Do connections pile up? Are they doing
sorting?
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
Order MySQL Network from
http://www.mysql.com/network/
"Heikki Tuuri" <Heikki.Tuuri@innodb.com> kirjoitti
viestissä:lfdWd.32$Le6.21@read3.inet.fi...
> Eddie,
>
> what does
>
> ulimit -a
>
> print?
>
> If you monitor the mysqld process size with the 'top' command, how big is
> it?
>
> Clearly, InnoDB is not the root of the problem, as it has only allocated
> 600 MB of memory.
>
> You can try setting tmp table size even lower.
>
> Best regards,
>
> Heikki Tuuri
> Innobase Oy
> Foreign keys, transactions, and row level locking for MySQL
> InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up
> MyISAM tables
>
http://www.innodb.com/order.php
>
> Order MySQL Network from
http://www.mysql.com/network/
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables
http://www.innodb.com/order.php