On Thursday, October 16, 2003, at 01:36 PM, Jeremy Zawodny wrote:
On Wed, Oct 15, 2003 at 06:35:03PM -0400, Gabriel Ricard wrote:
On Wednesday, October 15, 2003, at 03:10 PM, Jeremy Zawodny wrote:
I'd be interested to know if you can get a test running that uses either a key_buffer or an innodb_buffer_pool in the 3.5GB range.
Interestingly enough, I can't seem to get MySQL to use more than 2GB of
RAM.
I get errors like this:
*** malloc: vm_allocate(size=2042925056) failed with 3 *** malloc[489]: error: Can't allocate region
Hmm. That's not promising.
I wrote a small C program to test malloc() and see just how much I could allocate, and I was able to get up to 3.5GB before being cut off by the OS, which leads me to believe that I should be able to use that much RAM for MySQL.
Yes.
I wonder why you got cut off at 3.5GB. I'd have expected OS X on 64bit hardware not to have the weird limitations that, say, FreeBSD or Linux with kernel reserved memory.
Something is wonky here...
Thanks for the info. I'd love to hear if you're successful getting MySQL to use more than 2GB. I'm gonna hunt around a bit more to see what others may know.
Thanks,
Success! Sort of...
I installed the dev seed for Panther 7B85 and tested that... and now it loves RAM. I got it up to about 3GB with the following config:
query_cache_size=1024M bulk_insert_buffer_size=256M tmp_table_size=128M sort_buffer=8M read_rnd_buffer_size=8M key_buffer=768M record_buffer=32M myisam_sort_buffer_size=512M innodb_buffer_pool_size=1024M innodb_additional_mem_pool_size=32M
However, for some reason, when I swapped the values key_buffer and query_cache_size to try and give key_buffer 1GB, it failed. I swapped the values back and it worked fine... odd.
- Gabriel
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
