Here is a recent experience I had while trying to improve the performance of my digital audio workstation.
Here is what I was working with...
AMD XP 2500
1G RAM at 333mhz
MSI mobo w/ nForce2 chipset K7N-Delta(no SATA)
Promise TX2000 PCI RAID controller(new)
Aardvark Q10 PCI audio controller card
2 WD 40G drives
2 WD 80G drives(new)
The Beginning
The system as it stood was fairly stable, but I was running out of space and had no data protection/backup plan(due to lack of space for backups.) I must admit I came into the situation pretty much ignorant of the capabilities of the controller. I had planned on setting up a 0+1 RAID so that I could get some of the performance increase along with the redundancy of mirroring. Also I needed more space for recording, hence the 80G drives. I figured that with the two 80's I would end up with 120G of space in the 0+1 RAID configuration. Much to my chagrin the completed array only showed 80G available. So I dug into the manual and sure enough even though they are stripping the controller will shave the larger drives down to match the smallest drive in the array. One bummer out of the way I moved on to reinstalling my OS's(one for regular use and one for recording) and software. I ran SIsoft Sandra and WinBench and found that there was absolutely no performance boost when using 0+1. So I try to be optimistic about the situation and think to myself that at the least I am getting some fault protection.
Application
So the big day comes and I am trying to record the band. A minute into recording an error pops up on the screen saying the the tracks could not be saved because the disk may be full. This is sort of a generic error in Cakewalk Sonar that is saying that it couldn't write to the disk when it wanted. No amount of buffer tweaking in the program could get us past that error and the session was called off. No amount of tweaking could get the Sonar to record for more than 3 minutes. The cards are not sharing IRQs, per the BIOS. I tried using Powerstrip to modify PCI latency on the three cards in my machine. I tried giving first the RAID card priority and then the audio card, always leaving the graphics card to bring up the rear. Finally I removed the RAID and went with just the two 80G drives.
One 80 for OS and programs and one for audio data = Perfect
The Aftermath
So I am back in the same boat as far as protecting my data, but I can at least use my system as intended. I plan on making lemons into lemonade, if this RAID card will work with the BSD or Linux boxes on my network there is my backup solution. I don't look forward to backing up 40 to 50G over a network, but I suppose I will live.
Here is what I was working with...
AMD XP 2500
1G RAM at 333mhz
MSI mobo w/ nForce2 chipset K7N-Delta(no SATA)
Promise TX2000 PCI RAID controller(new)
Aardvark Q10 PCI audio controller card
2 WD 40G drives
2 WD 80G drives(new)
The Beginning
The system as it stood was fairly stable, but I was running out of space and had no data protection/backup plan(due to lack of space for backups.) I must admit I came into the situation pretty much ignorant of the capabilities of the controller. I had planned on setting up a 0+1 RAID so that I could get some of the performance increase along with the redundancy of mirroring. Also I needed more space for recording, hence the 80G drives. I figured that with the two 80's I would end up with 120G of space in the 0+1 RAID configuration. Much to my chagrin the completed array only showed 80G available. So I dug into the manual and sure enough even though they are stripping the controller will shave the larger drives down to match the smallest drive in the array. One bummer out of the way I moved on to reinstalling my OS's(one for regular use and one for recording) and software. I ran SIsoft Sandra and WinBench and found that there was absolutely no performance boost when using 0+1. So I try to be optimistic about the situation and think to myself that at the least I am getting some fault protection.
Application
So the big day comes and I am trying to record the band. A minute into recording an error pops up on the screen saying the the tracks could not be saved because the disk may be full. This is sort of a generic error in Cakewalk Sonar that is saying that it couldn't write to the disk when it wanted. No amount of buffer tweaking in the program could get us past that error and the session was called off. No amount of tweaking could get the Sonar to record for more than 3 minutes. The cards are not sharing IRQs, per the BIOS. I tried using Powerstrip to modify PCI latency on the three cards in my machine. I tried giving first the RAID card priority and then the audio card, always leaving the graphics card to bring up the rear. Finally I removed the RAID and went with just the two 80G drives.
One 80 for OS and programs and one for audio data = Perfect
The Aftermath
So I am back in the same boat as far as protecting my data, but I can at least use my system as intended. I plan on making lemons into lemonade, if this RAID card will work with the BSD or Linux boxes on my network there is my backup solution. I don't look forward to backing up 40 to 50G over a network, but I suppose I will live.