[ale] Storing MySQL Database in memory

John C jcouncilman at knology.net
Mon Aug 13 11:30:28 EDT 2007


Check out heap tables.  This does exactly what you are looking for. They are
called memory tables now though.

http://dev.mysql.com/doc/refman/5.0/en/memory-storage-engine.html



On 8/12/07, Ashley Wilson <awilson at smartfurniture.com> wrote:
>
> I think there is a way you can do what you want using my.cnf... I tried it
> a over year ago for a previous employer, but they were using win server
> 2003, and we had trouble allocating more than 2GB to mysql.
>
> -----Original Message-----
> From: Christopher Fowler <cfowler at outpostsentinel.com>
> Sent: Sunday, August 12, 2007 5:13 PM
> To: ale at ale.org
> Subject: [ale] Storing MySQL Database in memory
>
> I had this idea that since I've upgraded the memory on one of our
> servers to 2.5GB that I could run the MySQL database from memory.  I'm
> not sure if there is a performance gain but I'm trying to figure out how
> I would do it and preserve the data on reboots.
>
> One idea I had was to create a 128mb ramdisk and a 128mb fs image.  I
> would then create a RAID1 array between those.  Since a RAID1 is a copy
> of the filesystem on reboot I could simply copy the fs.img to a backup
> and create a new array.  Once the array is created I could then format
> it and copy the data into it.  I think the only problem I see here is
> that writes will slow me down since the writes have to go back down to
> the disk.  How about reads.  The majority of the time the system is
> reading not writing.
>
> Chris
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>
-------------- next part --------------
An HTML attachment was scrubbed...




More information about the Ale mailing list