Why not go AMD-64? Dual Opteron, with 8/16/32 gig of RAM? Get a 3ware
SATA drive, and run Gentoo for AMD-64. You can increase your innodb
buffer pool to use almost all that space. You can make your buffer pool
as large as the physical RAM in your machine can support. No 2.5 gig per
process, 4-gig limit on addressable memory (without the address-extensions).
Your hardware is holding you back more than your operating system.
David
Brady Brown wrote:
Hi,
I am currently running a large database (around 20Gb) on a 32bit x86
Linux platform. Many of my larger data-crunching queries are
disk-bound due to the limitation described in the innodb configuration
documentation:
*Warning:* On 32-bit GNU/Linux x86, you must be careful not to set
memory usage too high. |glibc| may allow the process heap to grow over
thread stacks, which crashes your server. It is a risk if the value of
the following expression is close to or exceeds 2GB:
Being a responsible citizen, I have my innodb_buffer_pool_size set
below 2Gb. But the time has come to scale the application, so I need
an alternative solution that will allow me to set
innodb_buffer_pool_size as high as my heart desires (or at least well
beyond 2Gb).
Do any of you have battle-tested recommendations?
How about FreeBSD? From what I can gather, it is a good idea to build
MySQL on FreeBSD linked with the Linux Thread Library. Would doing so
re- invoke the 2Gb limit?
I look foward to your collective responses. Thanks!
Brady
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
