The table I'm using is non-critical data, so it's not really an issue for me. But I was browsing through the mysql manual looking for a way to rebuild an MYI file from the .frm and MYD file (is there a way?) when I came across this:
http://www.mysql.com/doc/en/CACHE_INDEX.html Index caches are only available in MySQL 4.11 unfortunately, so perhaps my ramdisk idea is a workaround for index caching until 411 is stable? On Mon, 2004-02-23 at 15:34, Eric B. wrote: > How are you ensuring syncronization between the ram disk and the HD? Is > there a writeback / writethrough mechanism for ram disks? Are you not > risking major data loss if ever you have a power failure or PC failure? > > Thanks for the info! > > Eric > > "Mark Maunder" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > Since HEAP tables don't support fulltext indexes, is moving MYISAM > > tables to ramdisk an acceptable workaround? > > > > On Sat, 2004-02-21 at 18:35, Mark Maunder wrote: > > > I've noticed a 4 times insert speed improvement by moving the MYI index > > > file of a myisam table to a ramdisk. The MYD file is still on a physical > > > disk, and I benchmarked the difference between moving just the index > > > file, or moving both, and it was only a 10% difference in speed. The > > > table has a large fulltext index. > > > > > > Has anyone else played with moving MYI files to ramdisk for performance? > > > Any caveats that you know of, besides running out of ramdisk space? > > > > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
