Guys, I have two questions that I hope someone would be able to answer.
First some backround, I'm running a standard debian package of mysql 4.1 (currently the latest version) with no my.cnf tweaks except turning on query caching (using the default values from the manual) and allowing for large heap tables (up to 500MB). I've been running the beast for a while now without any issues but recently mysqld started slowly eating up memory until it consumes the entire system memory. In the past because I'm using heap tables I've always watched mysql's memory consumption very closely and it was increasing very slowly as new rows are added to the heap table. My HEAP table is a mirror of a disk table Both are 150K rows in length while MySQL reports the HEAP table size is 160MB and MyISAM that is 50MB. So basically the questions are. 1. Why does the HEAP table take so much more physical space than the MyISAM table? 2. How can I trace the memory consumption from within mysql to know what's causing the huge spikes in consumption that eat my entire system memory? Usually my MySQL idles comfortably using 300MB resident and 300MB virtual memory though when all hell breaks loose memory usage surges to 1GB resident and a similar figure for virtual effectively eating my RAM and killing the system by swapping like mad. Any input would be greatly appreciated! __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
