On Sep 28, 2005, at 5:21 PM, Devananda wrote:
Jeff wrote: Lots of stuff goes in here...
So without going into specifics here... your sort_buffer and read_buffer become pretty much unimportant if you move everything to InnoDB... keeping in mind the earlier advice to leave the mysql database intact in myisam. So if you went that route you can set them to like.. 32k or something trivial and even the 250 x multiplier doesn't hurt you much here. Once you do that of course you should give InnoDB most of the memory.
On the disk side the one comment I didn't see is that if you have 2.2G of data already, you need 4.5G of InnoDB table space to put it all together. InnoDB needs (as a rough guideline) twice as much table space as there is data, so it can do things like indexes, and undo logs and so on... Your 2 x 2G files isn't going to cut it as a place to put your 2.2G of data. In your case for these guys I'd throw 3 x 2G files at it and a fourth auto extending file - more if you move your other tables... most of our database instances had 20 x 2G files in their InnoDB table space before we moved to innodb_file_per_table where it stopped being an issue.
Best Regards, Bruce -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
