should raid be the OS disk or another?

[justakid]

Just read Chainbolts kool guide, but i just wanna know, is it advisable to have the raid array be the OS drive? or another?

Reason I ask is because I am getting into video editing and was gonna use this drive as the 'temp/working drive' for video editing.

Anyone got any tips on this? or are any optimum settings I can use for a video editing/3D machine? (and on the slight ocassion gaming

[chainbolt]

Originally posted by justakid
Just read Chainbolts kool guide, but i just wanna know, is it advisable to have the raid array be the OS drive? or another?

Reason I ask is because I am getting into video editing and was gonna use this drive as the 'temp/working drive' for video editing.

Anyone got any tips on this? or are any optimum settings I can use for a video editing/3D machine? (and on the slight ocassion gaming

Put the OS on the RAID array. You feel (shlightly) the difference already when you boot into the OS. If video editing is your main purpose you should consider a 32K/32K set up.

In case you run software RAID (without a RAID) by Window's Dynamic Disk functions you anyway don't have a choice: the OS cannot be installed on the RAID array, because it's the source of the array.

[justakid]

gonna be using Epox onboard raid... - 32/32?

Some people have told me to make the raid setup the paging file drive/storage drive where the work is gonna occur... any opinion on this?

[justakid]

so do u guys reckon this would be an ok setup?

raid using onboard controller of 4pea+.

make the raid setup the OS drive. place the swap memory on another HD. make the OS the working HD for video editing apps (ie the drive which is used to store temp video files etc)

thanks

[chainbolt]

Originally posted by justakid
so do u guys reckon this would be an ok setup?

raid using onboard controller of 4pea+.

make the raid setup the OS drive. place the swap memory on another HD. make the OS the working HD for video editing apps (ie the drive which is used to store temp video files etc)

thanks

This with the swap file on a different HDD is from times when we had slow and small disk and little RAM. The more RAM you have the less important is swap file and the less you should use it, because it's much slower than RAM.

Put the OS AND the swap file (which should be as small as possible if you have enough RAM) on the first partition of your RAID 0 array, this partition should be around 5~10 MB. Then put all your applications on another partition. This way you

(a) have the OS on the fastet part of the RAID array (outermost)
(b) prevent fragmentation of the OS and the swap file

But even this will not make any noticable difference.

[eva2000]

Originally posted by chainbolt


This with the swap file on a different HDD is from times when we had slow and small disk and little RAM. The more RAM you have the less important is swap file and the less you should use it, because it's much slower than RAM.

Put the OS AND the swap file (which should be as small as possible if you have enough RAM) on the first partition of your RAID 0 array, this partition should be around 5~10 MB. Then put all your applications on another partition. This way you

(a) have the OS on the fastet part of the RAID array (outermost)
(b) prevent fragmentation of the OS and the swap file

But even this will not make any noticable difference.

5-10GB i hope you mean

[justakid]

he i was about to ask that eva glad u did before me

man gonna have to read through the guide again before i set up...


argh.. man i just wanna get my stuff and install it.. dont wanna slow down and make sure everything is right? hjehhe

I just got the and p4 chip enermax psu.. man they look kool

waiting for MB RAM AND HD damnit

[chainbolt]

Originally posted by justakid
he i was about to ask that eva glad u did before me

man gonna have to read through the guide again before i set up...


argh.. man i just wanna get my stuff and install it.. dont wanna slow down and make sure everything is right? hjehhe

I just got the and p4 chip enermax psu.. man they look kool

waiting for MB RAM AND HD damnit

There is NO general set up rule Half a year ago we had 1000 post therad at amdmb.com about cluster and block stripe size. ppl started flaming each other because everybody got different results with the set up which was decalred as high performing by somebody else. At the end it was clear that of you bench HDD with applications you will find that every HDD, every chipset, every RAID controller (and there combinations) has it's own story.
If this is really important for you, you have to find the best solution for you individually for your system. HDD/RAID optimization can take a LONG time, because changing cluster/stripe size means always re-installing the OS and then re-benching.

[wipeout]

Originally posted by chainbolt
Put the OS AND the swap file (which should be as small as possible if you have enough RAM) on the first partition of your RAID 0 array, this partition should be around 5~10 MB.

It's normally a good idea to keep the boot partition (most commonly also the OS partition) <7.8GB in size, as it will prevent a future hotfix or Service Pack from putting file blocks that are required for boot-up beyond the addressable 7.8GB mark.