«
»

MySQL/64-bit and memory allocation

Posted on 1/3/2006, 11:44 pm, by Colin Charles, under MySQL.

So, earlier today I was playing around with compiling MySQL on a 64-bit platform, as there was a bug reported that there were problems allocating a large amount of memory to it. I compiled it, and tried running a few tests beyond the usual make test to see if I could make it run into problems.

I couldn’t. From a chat earlier in the morning, Stefan told me to try a really large table, with a stored procedure that repeatedly queried it. I tried that, but never got my out of memory errors. And my test box had 1GB of RAM.

So my question to readers are:

  1. Have you had grief with MySQL 5 (or later, see 5.1 just hit beta) on a 32-bit or 64-bit platform, where you had issues allocating a large amount of memory to the MySQL server?
  2. Do you have useful test harnesses designed to stress test your greatest/latest/newest database installation? How do you, the community QA the next release of MySQL?

If you answered yes to any of the above, do drop me e-mail at colin@mysql.com, or comment here. Thanks.

In other interesting news, Jay, my colleague presented a webminar on Coding and Indexing Strategies for Optimal Performance. It was well received, I had a really good time attending it (even though it was at 5am!) and I suggest folk going to these webminars. Sure, it requires an icky Java client, but you do learn a lot following presentations and listening to the presentation. Its like a recorded lecture/podcast, except its all automated :)

Oh, and MySQL 5.1 just hit beta. Seeing my iPod 3G died, maybe its time to make MySQL rock and win an iPod Nano. File reproducible bug reports, talk about it, and get picked to win an iPod Nano. 1 given away every week!
(yes, yes, I know I can’t get to win an iPod Nano)

3 Comments

  1. root says:
    2/3/2006 at 3:11 am

    Hello,
    I don’t mean to be dumb, but did you test over the 32 bit memory limit?

  2. Bubba says:
    2/3/2006 at 4:58 pm

    I’ve done the compile on a 16GB 2x dual core Opteron DL385 server, and allocated 14G to cache for InnoDB. Worked for me with a 12GB database. Got a link to the bug report?

    I did lose some server time due to the kernel I was using and the lack of HPTE support in the DL385 – but that’s another issue.

  3. byte says:
    2/3/2006 at 6:24 pm

    Yea, but I’ve gotten more insight to that said out of memory problem. Will blog about it later

«
»
i