Mark Maunder wrote:
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:
There is:
REPAIR TABLE t1 USE_FRM
--
Sasha P
Hi Mark,
- Original Message -
From: "Mark Maunder"
Sent: Monday, February 23, 2004 4:17 PM
Subject: Re: HEAP tables vs MYISAM on ramdisk
> 411 is packed with features I'm dying to have on my production server,
> but I had it on my dev box, and I got some t
411 is packed with features I'm dying to have on my production server,
but I had it on my dev box, and I got some table corruption which,
admittedly, I was too lazy to try to reproduce. So I've downgraded to
production 4 again. I have a heavily updated fulltext index which may be
the root of the ev
Index caches are new to 4.1.x, but key caches have been around for a while.
Definitely in 4.0, can't remember about 3.x. Either way though, I don't see
either helping with inserts or updates. Only with queries.
MySQL does suggest using a seperate key cache for temporary tables though:
http://www
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 on
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
ne
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
