Per, I remember someone also reporting a problem that glibc or Linux does not allow creation of new threads if one has allocated >= 2 GB user memory. I think there are problems in where the OS places the excutable, thread stacks, etc.
So it is uncharted territory. Oracle seems to have an option to use AWE memory on the Red Hat Advanced Server. Then the limit is 64 GB on a 32-bit Intel processor. InnoDB-4.1 has the same AWE option, but only on certain Windows versions. If Itanium and Opteron fail to take off, or a feature sponsor appears, I may consider implementing AWE also on Linux. The memory crunch is getting so severe that I believe some 64-bit processor must become common by 2005. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Transactions, foreign keys, and a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ ----- Original Message ----- From: "Per Andreas Buer" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Wednesday, June 04, 2003 1:21 PM Subject: malloc'ing 2GB+ of memory in mysql > Hi > > The Mysql binary distribution for IA32-linux is statically linked with > glibc. glibc malloc limits memory allocations to 2GB, which means that a > buffer in mysql can't grow beyond 2GB. This is due to some paranoia in > glibc malloc - they don't rely on the size to be an unsigned int - which > limits the size to 2^31 on any 32-bit platform. > > Has anyone tried to remove this limit in glibc malloc or linking Mysql > with another malloc implementation? > > -- > Per Andreas Buer > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
