So sprach �Ron Johnson� am 2001-07-22 um 16:57:12 -0500 :
> Therefore, bottom line: any parts of your database that you use
> will be brought into the OS's RAM cache, and RAM in a cache or
> RAM in a RAM disk is still RAM, so no need for RAM disk.
Almost true - except: Writing to RAM will always be *WAY* faster than
writing to a hard disk. And if there's more than enough RAM, reading
from a RAM Disk is actually not such a bad idea at all, even given the
fact that inodes are cached in RAM. BUT: What happens if you want to
read from an uncached inode? Exactly - you gotta read from the disk,
which will ALWAYS be a *LOT* slower than reading from RAM.
This having said: If the original poster is using MySQL, I'd also hint
to look at HEAP tables. Those are tables which are stored completely in
RAM. Problem with heap tables: auto_increment columns don't work and
shutting down the server will lose all the contents in the heap table.
Alexander Skwar
--
How to quote: http://learn.to/quote (german) http://quote.6x.to (english)
Homepage: http://www.digitalprojects.com | http://www.iso-top.de
iso-top.de - Die g�nstige Art an Linux Distributionen zu kommen
Uptime: 0 hours 34 minutes
