On 25 Mar 2004, at 06:31, Heikki Tuuri wrote:
you can use the command
SHOW INNODB STATUS;
to check how much memory InnoDB has allocated in total. Please report what
it says at the time of the memory explosion.
Well, that was informative, but in a negative sort of way. SHOW INNODB STATUS produced identical output when run immediately after server startup and when 50 idle connections were in place, and the virtual memory consumption had increased by around 2GB.
You report that even 100 IDLE connections cause the memory explosion. I
agree with Sasha that this probably is not a MySQL/InnoDB bug. I have not
heard of a similar memory problem from anyone else.
No, indeed. I'm going to try building mysql myself, on the machine on which it's going to be running, and see whether that still has the issue...
Tim
-- Dr Tim Cutts Informatics Systems Group Wellcome Trust Sanger Institute Hinxton, Cambridge, CB10 1SA, UK
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
