> best to test first with a borrowed Opteron. I want to see the stability
and
> that fsync() and other kernel calls work fast. A customer tested recently
a
> big Itanium II box and its performance looked ok.
Tom's Hardware did some benchmarking of MySQL 3.23.52 with the Opteron:
http://www.tomsha
Owen,
- Original Message -
From: "Owen Scott Medd" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, June 04, 2003 3:13 PM
Subject: Re: malloc'ing 2GB+ of memory in mysql
> I know we are fac
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.mysq
Hello Heikki,
"Heikki Tuuri" <[EMAIL PROTECTED]> writes:
> 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.
nal 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
&g
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
