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
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. I just can't seem to get it to do so. I even tuned down all of the other configuration options so that MySQL was only using about 30MB of RAM with a key_buffer of 0MB. Then I bumped up the key_buffer to 3.5GB: no go, 3GB: no go, 2.75GB: no go, 2.5GB: nope, 2250MB: yes! 'top' reports mysql to be using 255MB at that level.
So, yeah, I can run some benchmarks on that... But I don't see how useful they'd be since all of the other parameters are tuned way down. (none are over 8MB) InnoDB benchmarks may be useful since it uses the buffer to cache records as well as keys.
- Gabriel
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
