On Dec 15, 2011, at 12:02 PM, Reindl Harald wrote: > this is NOT a memory issue > > 'myisam_use_mmap' in mysqld is buggy since a long time > http://bugs.mysql.com/bug.php?id=48726
This is fixed in 5.1.61, 5.5.20, 5.6.5: http://dev.mysql.com/doc/refman/5.6/en/news-5-6-5.html > we are speaking of a HP ProLiant DL 380G7 in a VMware-Cluster > with 36 GB ECC-RAM while there are machines using InnoDB > with 'large-pages' and some GB buffer_pool_size on the same > host and not about some customer hardware > > Am 15.12.2011 18:22, schrieb Andrés Tello: >> When I had memory issues, with something relatively stable, mostly is due >> faulty ram... >> >> Can you use or less ram or change fisically the ram? >> >> On Thu, Dec 15, 2011 at 2:23 AM, Reindl Harald <h.rei...@thelounge.net>wrote: >> >>> Am 15.12.2011 08:47, schrieb Rob Wultsch: >>>> To be brutally honest, if you want stability you should >>>> not be using MyISAM >>> >>> this is bullshit >>> >>> without 'myisam_use_mmap' i never saw mysqld crashing >>> in the past 10 years, independent of the storage engine >>> >>>> much less a not particularly commonly used feature. >>> >>> mmap is not rocket science, so i do not understnd why this >>> is not properly debugged and DEFAULT on > -- Paul DuBois Oracle Corporation / MySQL Documentation Team Madison, Wisconsin, USA www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
