NOTE: "nzb" translates to "seriously thrashes disks for huge file patches, unraring/recompressiong 10/20/30 GB at a time across 1000s of files, etc).
The hardware is able to handle all of that, considering I do it now with slower drives, slower ram, less ram, and an Q9450.
The new hardware is (I guess only the controllers matter with how I'll be using the Pools):
Intel Core i7 930 overclocked to 3.73 Ghz (boost to 4.1 Ghz) even with hyper-threading.
I've been rock stable with this board and CPU and overclock for 3 years as a developer machine.
12 GB 1600 Mhz ram
Intel ICH10R with two separate RAID1 arrays
2x RAID1 arrays
1x "scratch" drive for nzb thrashing
1x "backup" drive, for any and all backups (either Windows Server backup, or attached to the W2012E VM, etc).
2x IBM M1015 controllers flashed to LSI firmware (16 ports + ability for an expander in the future)
Not too worried about the throughput of the RAID1 arrays with the VMs. They aren't that busy anyhow.
Lastly, I do plan on about 20% of my DrivePool to be mirrored/folder redundant across about 5 or 6 disks by my estimates (sure, spread out to even more perhaps - see below).
So, my questions to the community/developers:
How well does DrivePool and Scanner work with a CPU that is going to be taxed off and on?
Should I focus on creating multiple DrivePools? One for the bottomless blu-ray/movies shares, and one for all of my redundant folders?
Should I create separate DrivePools for each extremely large folder duplication? Think TV shows across about 40 different series, nearly all in large HD format.
The advantage to running my nzb utilities (which are very CPU and I/O intensive) in a VM is that I can throttle down the CPU usage and limit the threads it uses as virtual cores. Again, it will be all limited to the scratch drive on the ICH10R controller (for now).
Question
eduncan911
I am building a new home server that will serve several purposes:
The hardware is able to handle all of that, considering I do it now with slower drives, slower ram, less ram, and an Q9450.
The new hardware is (I guess only the controllers matter with how I'll be using the Pools):
Not too worried about the throughput of the RAID1 arrays with the VMs. They aren't that busy anyhow.
Lastly, I do plan on about 20% of my DrivePool to be mirrored/folder redundant across about 5 or 6 disks by my estimates (sure, spread out to even more perhaps - see below).
So, my questions to the community/developers:
The advantage to running my nzb utilities (which are very CPU and I/O intensive) in a VM is that I can throttle down the CPU usage and limit the threads it uses as virtual cores. Again, it will be all limited to the scratch drive on the ICH10R controller (for now).
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.