Hi Heikki.
"Heikki Tuuri" <[EMAIL PROTECTED]> writes:
> Why does InnoDB allocate so much memory in your case? If you follow
> the memory allocation with innodb_monitor, does the allocation grow
> steadily over days? Then it could be a memory leak in InnoDB.
This might be the case. I started MySQL with a very big
additional_mem_pool (400M) as you suggested. The server ran very stable
for 12 hours. At first, memory allocation was like this:
Total memory allocated 1499024287; in additional pool allocated 1205632
Total memory allocated 1499024287; in additional pool allocated 1651072
Total memory allocated 1499024287; in additional pool allocated 1815808
Total memory allocated 1499024287; in additional pool allocated 1887488
Total memory allocated 1499024287; in additional pool allocated 1962880
Total memory allocated 1499024287; in additional pool allocated 2005504
Total memory allocated 1499024287; in additional pool allocated 2029056
Total memory allocated 1499024287; in additional pool allocated 2060288
Total memory allocated 1499024287; in additional pool allocated 2068352
Total memory allocated 1499024287; in additional pool allocated 2106496
12 hours later:
Total memory allocated 1499024287; in additional pool allocated 4044928
Total memory allocated 1499024287; in additional pool allocated 4049792
Total memory allocated 1499024287; in additional pool allocated 4046208
Total memory allocated 1499024287; in additional pool allocated 4038912
Total memory allocated 1499024287; in additional pool allocated 4049792
Total memory allocated 1499024287; in additional pool allocated 4048000
Total memory allocated 1499024287; in additional pool allocated 4046464
Total memory allocated 1499024287; in additional pool allocated 4046080
Total memory allocated 1499024287; in additional pool allocated 4043264
Total memory allocated 1499024287; in additional pool allocated 4046080
Total memory allocated 1499024287; in additional pool allocated 4049024
Total memory allocated 1499024287; in additional pool allocated 4059008
Total memory allocated 1499024287; in additional pool allocated 4067200
Total memory allocated 1499024287; in additional pool allocated 4063744
Total memory allocated 1499024287; in additional pool allocated 4049792
Total memory allocated 1499024287; in additional pool allocated 4061952
(The reason the server crashed was due to many threads - we had approx
350 threads and we hit the 2GB barrier with a bang).
> 1) Monitor the memory consumption with innodb_monitor. Is there a symptom of
> a memory leak?
I will get back to you on this one ~ friday when I have more data.
> 2) Try a smaller buffer pool or bigger. Does the crash always happen when
> InnoDB has allocated about 1400 MB of memory?
> 3) Try setting innodb_additional_mem_pool much bigger, say, 400 MB. Does
> memory allocation still spill over from it?
No. It runs very stable with a much bigger innodb_additional_mem_pool.
Looks the problem is linked with increasing the size of the
innodb_additional_mem_pool.
Greetings,
--
Per Andreas Buer
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
