On Wednesday 12 July 2006 01:13 pm, Tim Lucia wrote: > I've seen whitepapers from MySQL's web site, co-authored with Dell, that > recommend the hardware optimization be: > > 1. More Memory > 2. Faster Drives (15K RPM is better the 10K) > 3. Faster CPU.
Oh wait, we forgot #4: > 4. Filesystem You can have the fastest disk alive, but if your filesystem is doing sleep(1000) during every transfer (this is 1% possible, but just an example), you're data transfer is just plain going to suck. There's a couple of Filesystems out there: Ext2/3 I recommend ext3 here. It's tried and true tested throughout the business world, kind of slow at times, but mostly stable in the end. You'll generally see this as the filesystem of choice for those running *NIX type systems. XFS This one does a lot of operations in memory, and tries to write to disk as infrequently as possible, instead caching it in memory. This does wonders for transfer rates, but just remember, memory is a temporary storage. If your power goes out, kiss your data goodbye! If you still want performance, at least put your server behind a nice UPS! JFS I use this at home a lot, and it works fairly well. It seems to be a nice mix of speed and stability. When something does go wrong, fsck takes under 30 seconds on a 30GB drive. Unfortunately this doesn't have too much corporate world exposure like ext2/3. Good for when you're bored on a sunny Tuesday and want to try something new out. Fat32/NTFS Well, this is kind of a quick answer. Most will straightup go "NTFS" nowdays (iirc because of speed and security labels, but I haven't dealt with windows filesystems in awhile). -- Chris White PHP Programmer/DBooyah! Interfuel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
