Azu Posted June 21, 2007 Share Posted June 21, 2007 Please tell me how to make it so that as soon as MySQL starts, all of my MyISAM and InnoDB tables are loaded into RAM so that after that they don't have to be read from disk (and any changes to them are made to the one in the RAM and also committed to disk) Quote Link to comment Share on other sites More sharing options...
Azu Posted June 21, 2007 Author Share Posted June 21, 2007 What??? Quote Link to comment Share on other sites More sharing options...
kenrbnsn Posted June 21, 2007 Share Posted June 21, 2007 The original first reply, now deleted, was spam. The spammer has been banned and the posts that were made are being deleted. Ken Quote Link to comment Share on other sites More sharing options...
Azu Posted June 23, 2007 Author Share Posted June 23, 2007 Oh okay thanks for banning him. Damn spammers >_< Quote Link to comment Share on other sites More sharing options...
Azu Posted June 30, 2007 Author Share Posted June 30, 2007 Hmm could somebody please answer my original question though? I'd really appreciated it Quote Link to comment Share on other sites More sharing options...
fenway Posted July 1, 2007 Share Posted July 1, 2007 I'm not sure what you mean... Quote Link to comment Share on other sites More sharing options...
Azu Posted July 2, 2007 Author Share Posted July 2, 2007 I want all of the data in my mysql database to be loaded into memory at startup. This way once it starts up, everything is done in memory, and there is no disk I/O overhead. I would like any changes made to be committed to disk once in a while though, in case of a power problem. And also committed to disk at shutdown. Is this possible? Any help would be very appreciate Quote Link to comment Share on other sites More sharing options...
Wildbug Posted July 2, 2007 Share Posted July 2, 2007 You can create a RAM disk, copy your database files to it, and start MySQL. It doesn't do much for writing it back to disk, however. You can write a script+cron to occasionally back it up/before shutdown. Alternatively, you can (and this is almost needlessly complex) have two tables, one on disk, one in RAM -- created from disk at startup -- do just SELECTs from the in-RAM database and writes to both. If you're truly strapped for performance and have a database with heavy read traffic, that might help. In this way, writes are always committed to disk. Quote Link to comment Share on other sites More sharing options...
Azu Posted July 3, 2007 Author Share Posted July 3, 2007 Thank you, I will try both ways and see what one is faster Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.