List:General Discussion« Previous MessageNext Message »
From:Scott Hess Date:October 4 1999 5:02pm
Subject:Re: MySQL in memory
View as plain text  
randyboy <randyboy@stripped> wrote:
> Thanks for all the responses.  However, I'm still wondering, in the heap
> method and in the stick-bit copy all into memory method, how does one
> maintain synchronicity between the db on disk and the copy in memory?

One solution using a ramdisk would be to spool update logs to the real
disk.  On boot, start a mysql on the real disk's database, push the update
logs through that mysql, bring it back down, copy the real files to the
ramdisk, and then bring up mysql on the ramdisk tables.  [Or, copy the real
files to the ramdisk, run the update log, copy the ramdisk files back out
to disk, and then let people start whacking the ramdisk version.
Whichever.]

I once actually considered doing this as a cheap variant on using a
solid-state SCSI disk.  Unfortunately, my performance concerns all related
to lots of data, and even a 4Gig ramdisk just wouldn't suffice.

Later,
scott


Thread
MySQL in memoryrandyboy2 Oct
  • Re: MySQL in memoryAlistair MacDonald2 Oct
    • Re: MySQL in memoryJani Tolonen3 Oct
  • Re: MySQL in memorysinisa3 Oct
    • Re: MySQL in memoryRobert Hazeltine3 Oct
    • Re: MySQL in memoryRobbin Zhang3 Oct
      • Re: MySQL in memoryJani Tolonen3 Oct
        • Re: MySQL in memoryRobbin Zhang3 Oct
          • Re: MySQL in memoryrandyboy3 Oct
            • Re: MySQL in memoryMatthias Urlichs4 Oct
            • Re: MySQL in memorysinisa4 Oct
            • Re: MySQL in memoryScott Hess4 Oct
      • Re: MySQL in memorysinisa4 Oct